From: ebiederm@xmission.com (Eric W. Biederman)
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-revover-tags-script
Date: Sun, 17 Jul 2005 23:40:28 -0600 [thread overview]
Message-ID: <m164v8oenn.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <7v64v8j4qn.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Sun, 17 Jul 2005 18:13:36 -0700")
Junio C Hamano <junkio@cox.net> writes:
> ebiederm@xmission.com (Eric W. Biederman) writes:
>
>> Actually looking a little deeper unless I have misread
>> the code git-fetch-pack at least will only ask for commit
>> objects so git fetch will never return a tag object.
>
> I thought so but then I tried it and actually it does seem to
> work as expected (well, it is Linus code so it has to be perfect
> ;-).
Yep. I confused the want and have cases when I was reading
the code.
A generalization of git-fetch-pack that can handle multiple
heads looks like it would handle the transfer part of the
problem with tags. git-clone-pack already does. Then
all that is needed is a sane way to list the heads that
are read back and some post processing to install everything.
The big question is in what format should we return the heads?
Just a space separated list of sha1's or a directory hierarchy
like git-clone-pack uses.
Eric
next prev parent reply other threads:[~2005-07-18 5:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 20:20 [PATCH] git-revover-tags-script Eric W. Biederman
2005-07-17 0:51 ` Junio C Hamano
2005-07-17 8:40 ` Eric W. Biederman
2005-07-17 18:53 ` Junio C Hamano
2005-07-18 0:06 ` Eric W. Biederman
2005-07-18 1:13 ` Junio C Hamano
2005-07-18 5:40 ` Eric W. Biederman [this message]
2005-07-18 6:36 ` Junio C Hamano
2005-07-18 0:19 ` Eric W. Biederman
2005-07-20 0:20 ` [RFD] server-info to help clients Junio C Hamano
2005-07-20 0:35 ` David Lang
2005-07-20 1:53 ` 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=m164v8oenn.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).