From: Tom Prince <tom.prince@ualberta.net>
To: Junio C Hamano <junkio@cox.net>
Cc: Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: Cogito: cg-clone doesn't like packed tag objects
Date: Mon, 26 Sep 2005 23:02:36 -0600 [thread overview]
Message-ID: <8764snyufn.fsf@ualberta.net> (raw)
In-Reply-To: <7vr7bb5d8w.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
> Petr Baudis <pasky@suse.cz> writes:
>
>> Yes - so you can't save the tag objects either, but then
>> you'll re-slurp them again and again, which is kind of
>> silly. Alternatively, you could actually make git-fsck-object
>> silent about the case when an unreachable (not referenced in
>> refs/) tag object references a non-existing object - perhaps
>> unless --strict is passed to it. If you think the rest of my
>> logic is ok, I think this change to facilitate this "tags
>> caching" is not unreasonable.
>
> Now you completely lost me. I really do not understand what you
> mean by tags caching and re-slurping.
>
I think Petr is interested in the case where the user hasn't asked for a
particular tag. He wants to automatically grab all the tags in a repository,
or at least those that refer to a branch being downloaded.
Of course, if somebody asks for a specific tag, then everything necessary
should be downloaded. Somebody is fetching your maint branch, Petr want to
automatically download all the tags v0.99.7[a-d], without the user specifying
them explicitly. Or more complex, somebody is tracking your master but NOT
maint. Then Petr wants to download tags v0.99.[0-9] but not v0.99.7[a-d].
Tom
next prev parent reply other threads:[~2005-09-27 5:03 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8764snyufn.fsf@ualberta.net \
--to=tom.prince@ualberta.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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 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 NNTP newsgroup(s).