All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Zeh <robert.allan.zeh@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Git svn fetches entire trunk on tags (change from 1.6.5.2 to 1.7.0)
Date: Tue, 16 Feb 2010 19:17:47 -0600	[thread overview]
Message-ID: <94a51d821002161717q4dd116f9tebff3a2475446a8e@mail.gmail.com> (raw)

Since upgrading from 1.6.5.2 to 1.7.0 I've noticed a change in how
git svn fetches from the Subversion repository on tags.  Of course,
for the repo I'm working with there are many more tags then branches.
1.6.5.2 gives me the following on a tag:


r333 = b15f3f20710a1e282fb6ff62c13fad64376ad2b4 (refs/remotes/trunk)
Found possible branch point:http://bt011us013s/prod_repos/trunk
=>http://bt011us013s/prod_repos/tags/3.09.1255, 333
Found branch parent: (refs/remotes/tags/3.09.1255)
b15f3f20710a1e282fb6ff62c13fad64376ad2b4
Following parent with do_switch
Successfully followed parent

r334 = 77d132d69bc333e7c988a4f3af9d48a98dadf0d4 (refs/remotes/tags/3.09.1255)

With 1.7.0:
r333 = b15f3f20710a1e282fb6ff62c13fad64376ad2b4 (refs/remotes/trunk)

        A       Enterprise/Header.txt
        ....

r334 = 2c0e6dd89e81e7d18288e135f40f193b2ff22018 (refs/remotes/tags/3.09.1255)

The SHA1s are also different.

It would be nice if the entire branch wasn't fetched.

Robert

             reply	other threads:[~2010-02-17  1:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17  1:17 Robert Zeh [this message]
2010-02-17 23:23 ` Git svn fetches entire trunk on tags (change from 1.6.5.2 to 1.7.0) Eric Wong
2010-02-17 23:54 Robert Zeh
2010-02-18  0:06 ` Eric Wong
2010-02-19 12:14   ` Robert Zeh

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=94a51d821002161717q4dd116f9tebff3a2475446a8e@mail.gmail.com \
    --to=robert.allan.zeh@gmail.com \
    --cc=git@vger.kernel.org \
    /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.