This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Acceptance criteria for the git conversion
- From: "Eric S. Raymond" <esr at thyrsus dot com>
- To: shmeel gutl <shmeelgutl at shmuelhome dot mine dot nu>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 3 Sep 2015 04:12:53 -0400
- Subject: Re: Acceptance criteria for the git conversion
- Authentication-results: sourceware.org; auth=none
- References: <20150901105414 dot GA30270 at thyrsus dot com> <55E7F4FE dot 2000805 at shmuelhome dot mine dot nu>
- Reply-to: esr at thyrsus dot com
shmeel gutl <shmeelgutl@shmuelhome.mine.nu>:
> On 01-Sep-15 01:54 PM, Eric S. Raymond wrote:
> >What kind of mechanical transformation or hand-editing would add value for you?
> I am working from a clone of the current git repository. Is there an
> automated procedure that will enable me to switch to the new repository and
> still keep all of the commit history of my local branches?
Fully automated, no. The closest possible approach to that would be a script
that took your branch point locations and branch names as arguments.
In that script, you should be able to turn your local branches into
patch sequences using git-format-patch, call git branch to create new
local branches in a clone of the conversion, and then apply the
sequences.
(I'm pretty sure there's also a way to do this using the obscure "git bundle"
feature, but I've never learned it in detail.)
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>