From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Petr Baudis <pasky@suse.cz>, Tom Prince <tom.prince@ualberta.net>,
git@vger.kernel.org
Subject: Re: Cogito: cg-clone doesn't like packed tag objects
Date: Tue, 27 Sep 2005 14:44:23 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0509271441210.3308@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0509271414000.3308@g5.osdl.org>
On Tue, 27 Sep 2005, Linus Torvalds wrote:
>
> Yes, it would work, but I really think that there's no downside to just
> having a
>
> git fetch --tags <dest>
>
> since that's just a few lines of trivial code, with no special cases.
Btw, there are upsides too. Remember how confused people were about your
very own v0.99.7a-d releases? They are _not_ on your main path, so those
tags wouldn't have been picked up even if Petr did his "pick up tags to
stuff you merge automatically" thing.
In fact, if you'd add "--tags" as some kind of automated flag in the
.git/remote/ file, then doing a "git fetch origin" could automatically
fetch tags by default, _without_ having the mistake of fetching them in
general (it probably _does_ make sense to track tags from the origin,
since you get the ones the origin had at "clone" time anyway).
Linus
next prev parent reply other threads:[~2005-09-27 21:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 22:24 Cogito: cg-clone doesn't like packed tag objects H. Peter Anvin
2005-09-24 1:18 ` Petr Baudis
2005-09-24 1:52 ` H. Peter Anvin
2005-09-24 2:00 ` Junio C Hamano
2005-09-24 12:50 ` Petr Baudis
2005-09-24 17:13 ` Daniel Barkalow
2005-09-24 18:10 ` Junio C Hamano
2005-11-09 22:33 ` Petr Baudis
2005-11-09 23:14 ` Junio C Hamano
2005-11-09 23:36 ` Nick Hengeveld
2005-11-09 23:44 ` Petr Baudis
2005-11-10 1:01 ` Nick Hengeveld
2005-11-09 23:47 ` Junio C Hamano
2005-09-26 21:25 ` Petr Baudis
2005-09-26 21:55 ` Brian Gerst
2005-09-26 21:56 ` Petr Baudis
2005-09-26 22:23 ` Junio C Hamano
2005-09-26 22:29 ` Petr Baudis
2005-09-27 4:46 ` Junio C Hamano
2005-09-27 5:02 ` Tom Prince
2005-09-27 5:28 ` Junio C Hamano
2005-09-27 9:40 ` Petr Baudis
2005-09-27 10:14 ` Josef Weidendorfer
2005-09-27 12:34 ` Petr Baudis
2005-09-27 13:27 ` Josef Weidendorfer
2005-09-27 17:07 ` Junio C Hamano
2005-09-27 17:56 ` Linus Torvalds
2005-09-27 18:36 ` Junio C Hamano
2005-09-27 21:16 ` Linus Torvalds
2005-09-27 21:44 ` Linus Torvalds [this message]
2005-09-27 22:11 ` Junio C Hamano
2005-09-28 17:22 ` Junio C Hamano
2005-10-14 6:03 ` Peeling the onion Junio C Hamano
[not found] ` <46a038f90510140048r30c7ec36n35f77a1ac52c4691@mail.gmail.com>
2005-10-14 8:40 ` Junio C Hamano
2005-09-26 22:37 ` Cogito: cg-clone doesn't like packed tag objects Junio C Hamano
2005-09-27 6:54 ` Sven Verdoolaege
2005-09-27 7:25 ` Ryan Anderson
2005-09-27 15:34 ` Linus Torvalds
2005-09-27 17:34 ` Ryan Anderson
2005-09-27 18:04 ` Linus Torvalds
2005-09-27 7:46 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0509271441210.3308@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
--cc=tom.prince@ualberta.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).