From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Linus Torvalds <torvalds@osdl.org>, walt <wa1ter@myrealbox.com>,
git@vger.kernel.org
Subject: Re: rsync deprecated but promoted?
Date: Mon, 26 Sep 2005 15:38:23 -0700 [thread overview]
Message-ID: <7vy85j8nfk.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0509261808530.23242@iabervon.org> (Daniel Barkalow's message of "Mon, 26 Sep 2005 18:13:43 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> I should actually implement that now that it's easy; you just skip the
> "for_each_ref(mark_complete);" on line 217 of fetch.c, and it'll make sure
> that it has everything.
>
> (I'll make a patch tonight if nobody beats me to it.)
Thanks.
next prev parent reply other threads:[~2005-09-26 22:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 16:32 rsync deprecated but promoted? Zack Brown
2005-09-25 17:07 ` H. Peter Anvin
2005-09-25 19:06 ` Martin Coxall
2005-09-26 13:32 ` Petr Baudis
2005-09-26 14:41 ` Brian Gerst
2005-09-26 16:36 ` Petr Baudis
2005-09-26 16:47 ` Brian Gerst
2005-09-26 15:04 ` Linus Torvalds
2005-09-26 16:38 ` Petr Baudis
2005-09-26 16:43 ` Linus Torvalds
2005-11-10 23:17 ` Petr Baudis
2005-09-26 16:44 ` walt
2005-09-26 17:55 ` Linus Torvalds
2005-09-26 19:23 ` walt
2005-09-26 20:12 ` Johannes Schindelin
2005-09-26 20:19 ` Junio C Hamano
2005-09-26 22:13 ` Daniel Barkalow
2005-09-26 22:38 ` Junio C Hamano [this message]
2005-09-26 20:43 ` Petr Baudis
2005-09-27 6:35 ` hared GIT repos (was Re: rsync deprecated but promoted?) Matthias Urlichs
2005-09-27 7:13 ` shared GIT repos Junio C Hamano
2005-09-27 8:45 ` Matthias Urlichs
2005-09-27 9:59 ` Sergey Vlasov
2005-09-27 10:29 ` Matthias Urlichs
2005-09-27 15:21 ` Linus Torvalds
2005-09-27 18:36 ` hared GIT repos (was Re: rsync deprecated but promoted?) 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=7vy85j8nfk.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=wa1ter@myrealbox.com \
/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).