You cannot do that.

I think there are some potential approaches:

  1. Copy perldb.pl into its own directory, and start a fresh git repository with it.
    This way you get a clean directory but lose all connection to the upstream. It is also easy to set up and understand. Importing changes from upstream will likely devolve into manually resolving diffs between bleadperl and your version.
  2. Clone the perl repository and ignore the rest of the files. This way, you can always resynchronize with the changes in Perl, at the cost of also synchronizing a lot of files you don't care about.
  3. Clone and then rewrite the perl git directory using git filter-branch to only transfer the history of perl5db.pl into the new repository. This way you keep all the file history of perl5db.pl and you can also periodically get a fresh version of the perl repository and export the perl5db.pl related patches to rebase your changes on it.
  4. Speak to p5p to spin off perl5db.pl from the core and make the CPAN version (to be released by you) upstream. This allows development to occur outside of the Perl core and the new perl5db.pl will then be periodically be copied into the perl repository.

In reply to Re: How to fork the debugger by Corion
in thread How to fork the debugger (GitHub) by LanX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.