From: Michael J Gruber <git@drmicha.warpmail.net>
To: Tobi <listaccount@e-tobi.net>
Cc: git@vger.kernel.org
Subject: Re: git-svn commit count vs- revision count
Date: Mon, 27 Jul 2009 11:59:08 +0200 [thread overview]
Message-ID: <4A6D7A6C.7020909@drmicha.warpmail.net> (raw)
In-Reply-To: <4A6D6916.2040509@e-tobi.net>
Tobi venit, vidit, dixit 27.07.2009 10:45:
> Hi!
>
> I've `git-svn clone`ed a pretty large repository, which took about 3 days
> even with with local access to the SVN repository. To check that
> everything went ok, I listed the root commits with `git fsck --root
> --full` and verfied, that these are indeed root commits with no branch point.
>
> So far so good... what's puzzling me is, that `git rev-list --all | wc -l`
> says I have 40731 commits, but the SVN repository only has 21875 revisons.
>
> Shouldn't these numbers be the same? The only explanation I have, is, that
> git-svn imported one or more branches or tags, where it failed to find the
> correct branch point in the history. Is there a way to figure out, if
> there went something wrong and possibly fix it?
With svn, it is possible to commit to (or create) several branches or
tags in one go (i.e. revision), whereas with git those would be
individual commits. For example, some people always create a commit and
a tag "pointing" to it in one go in svn (commit to trunk and tags/foo).
(The same is true for "svn style subprojects", i.e. subdirs used as
subprojects.)
If that has been used to a large extent then it may explain the
difference, although it is very large. Have you checked whether git-svn
produced the (number of) branches and tags that you expect?
Michael
next prev parent reply other threads:[~2009-07-27 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 8:45 git-svn commit count vs- revision count Tobi
2009-07-27 9:59 ` Michael J Gruber [this message]
2009-07-27 21:04 ` Tobi
2009-07-27 21:49 ` Tobi
2009-07-27 22:13 ` Tobi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A6D7A6C.7020909@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=listaccount@e-tobi.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.