[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Switching to bzr: what remains to be done?
|
From: |
Andreas Schwab |
|
Subject: |
Re: Switching to bzr: what remains to be done? |
|
Date: |
Tue, 09 Dec 2008 10:33:36 +0100 |
|
User-agent: |
Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux) |
Stefan Monnier <address@hidden> writes:
> I don't either. Andreas somehow manages to extract the merge info from
> the Arch archive and mix it up with the CVS data to generate&update its
> Git repository.
I didn't use Arch. The merge information was automatically extracted
from the commit messages, then manually fixed up.
Andreas.
--
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Re: Switching to bzr: what remains to be done?, Dan Nicolaescu, 2008/12/08
- Re: Switching to bzr: what remains to be done?, Karl Fogel, 2008/12/11
- Re: Switching to bzr: what remains to be done?, Karl Fogel, 2008/12/17
- Re: Switching to bzr: what remains to be done?, Tassilo Horn, 2008/12/18
- Re: Switching to bzr: what remains to be done?, Karl Fogel, 2008/12/18
- Re: Switching to bzr: what remains to be done?, Tassilo Horn, 2008/12/19
Re: Switching to bzr: what remains to be done?, Giorgos Keramidas, 2008/12/19
Re: Switching to bzr: what remains to be done?, Dan Nicolaescu, 2008/12/18