[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bzr repository ready?

From: Andreas Schwab
Subject: Re: bzr repository ready?
Date: Wed, 04 Feb 2009 21:48:39 +0100
User-agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)

Karl Fogel <address@hidden> writes:

>    "Spot-check a branch-sync change."

This is another merge commit that your tool appears to mishandle.  When
checking out the cvs trees before and after the change I see no
difference to the corresponding git trees, except that the files that
were renamed in this merge appear under both names in the older CVS
checkout.  The latter may be a limitation of cvs when checking out a
date, or it could be due to an invalid direct manipulation of the cvs
history (manually adding a branch tag instead of going through cvs

>    "Check that all tags are present."

These tags are all present in the git tree.  May be a bug in the
git->bzr conversion.

>    "Check that all branches are present."

Likewise, the branches are all present in the git tree.

The emacs-unicode branch has been absorbed by the emacs-unicode-2 branch.

The Boehm-versions branch was a short-lived branch containing only a gc
directory.  It appears to be a mistaken checkin, the commit that deleted
the files has the log message "Not committed to branch, sorry.".

The Ilya_4_35 branch appears to be the result of another git->bzr
conversion bug.  It is an ordinary tag in git.

The master branch is what CVS calls the HEAD branch.

The master-UNNAMED-BRANCH contains changes belonging to revisions that
are unreachable from any branch tag.  The name was constructed by
parsecvs since such unreferenced commits cannot exist in git.  Actually,
this branch combines several such anonymous branches, but parsecvs could
not tell them apart.


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."

reply via email to

[Prev in Thread] Current Thread [Next in Thread]