[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Git transition checklist
From: |
David Engster |
Subject: |
Re: Git transition checklist |
Date: |
Wed, 08 Jan 2014 19:17:03 +0100 |
User-agent: |
Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3 (gnu/linux) |
Eli Zaretskii writes:
>> From: Stefan Monnier <address@hidden>
>> Date: Wed, 08 Jan 2014 09:59:53 -0500
>> Cc: address@hidden
>
>>
>> > That's easy. Make a patch sequence from your bzr branch using sendto
>> > - the format is compatible with GNU patch. git checkout the branch
>> > name at the equivalent point in the git repo. Use GNU patch to apply.
>> > Fill in change comments as required.
>>
>> Sounds like a lot of manual work and it doesn't seem to preserve history
>> (e.g. merges that might have taken place). For a branch with a couple
>> commits that's probably OK, but with my 5 year-old branch it's
>> a non-starter, unless I misunderstand something.
>
> Indeed. I want to preserve the history of that branch, because it is
> work in progress that will land one day on the trunk. I don't want to
> see dozens of commits appear as a single jumbo commit after the
> migration. I'm quite sure I mentioned that in my original request.
If I understood Andreas correctly, all branches currently in the
Savannah repository are converted. So if you push this branch before the
switch, it should land in git as well?
-David
- Re: Improved git commit emails, (continued)
Re: Git transition checklist, Eric S. Raymond, 2014/01/08
Re: Git transition checklist, Eric S. Raymond, 2014/01/08
Re: Git transition checklist, Glenn Morris, 2014/01/08
Re: Git transition checklist, Eli Zaretskii, 2014/01/08
Re: Git transition checklist, Andreas Schwab, 2014/01/08
Re: Git transition checklist, Eli Zaretskii, 2014/01/08
Re: Git transition checklist, Andreas Schwab, 2014/01/08
Re: Git transition checklist, Stephen Berman, 2014/01/08