From: Shawn Pearce <spearce@spearce.org>
To: Jeff King <peff@peff.net>
Cc: A Large Angry SCM <gitzilla@gmail.com>,
Martin Waitz <tali@admingilde.org>,
Daniel Barkalow <barkalow@iabervon.org>,
git@vger.kernel.org
Subject: Re: Notes on Using Git with Subprojects
Date: Thu, 28 Sep 2006 00:09:31 -0400 [thread overview]
Message-ID: <20060928040931.GE22897@spearce.org> (raw)
In-Reply-To: <20060928040027.GA22489@coredump.intra.peff.net>
Jeff King <peff@peff.net> wrote:
> On Wed, Sep 27, 2006 at 11:58:55PM -0400, Shawn Pearce wrote:
>
> > If you are fetching a set of commits from a repository you probably
> > should be fetching any tags that point at the commits you've fetched.
> > They tend to be few compared to the commits, they tend to be small,
> > and they tend to be important milestones in the tracked project.
> >
> > I think that's why the native Git protocol sends tags for any
> > commits that were also sent. :)
>
> Oh, that's clever. :)
>
> Do we do the right thing for non-git transports?
Yes, I think we do.
Only its not quite as clever as the HTTP/FTP commit walker first
needs to get a list of available refs (which includes tag and
tag^{}) and compares each obtained commit to the ^{} entries.
If there's a match it gets the tag.
And rsync being as dumb as it is should be fetching everything. :)
--
Shawn.
next prev parent reply other threads:[~2006-09-28 4:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 17:40 Notes on Using Git with Subprojects A Large Angry SCM
2006-09-26 20:25 ` Johannes Schindelin
2006-09-26 22:01 ` A Large Angry SCM
2006-09-26 22:13 ` Johannes Schindelin
2006-09-26 22:45 ` A Large Angry SCM
2006-09-26 21:23 ` Daniel Barkalow
2006-09-26 21:30 ` Shawn Pearce
2006-09-26 22:33 ` A Large Angry SCM
2006-09-27 8:06 ` Martin Waitz
2006-09-27 9:55 ` Johannes Schindelin
2006-09-27 11:38 ` Martin Waitz
2006-09-27 12:01 ` Johannes Schindelin
2006-09-27 12:44 ` Sven Verdoolaege
2006-09-27 21:05 ` Junio C Hamano
2006-09-28 15:02 ` Michael S. Tsirkin
2006-09-28 20:16 ` Jeff King
2006-09-27 12:46 ` Martin Waitz
2006-09-27 13:13 ` Johannes Schindelin
2006-09-27 17:13 ` A Large Angry SCM
2006-09-27 23:14 ` Johannes Schindelin
2006-09-27 23:36 ` Shawn Pearce
2006-09-27 23:55 ` Rogan Dawes
2006-09-28 0:36 ` Shawn Pearce
2006-09-28 5:02 ` A Large Angry SCM
2006-09-28 4:48 ` A Large Angry SCM
2006-09-27 16:58 ` A Large Angry SCM
2006-09-27 17:33 ` Jeff King
2006-09-28 3:47 ` A Large Angry SCM
2006-09-28 3:52 ` Jeff King
2006-09-28 3:58 ` Shawn Pearce
2006-09-28 4:00 ` Jeff King
2006-09-28 4:09 ` Shawn Pearce [this message]
2006-09-28 3:52 ` Shawn Pearce
2006-09-28 15:39 ` Johannes Schindelin
2006-09-28 7:37 ` Martin Waitz
2006-09-28 20:30 ` A Large Angry SCM
2006-09-29 7:04 ` Martin Waitz
2006-09-26 22:07 ` A Large Angry SCM
2006-10-01 5:19 ` A Large Angry SCM
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=20060928040931.GE22897@spearce.org \
--to=spearce@spearce.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitzilla@gmail.com \
--cc=peff@peff.net \
--cc=tali@admingilde.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.