From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 0/4] The rest of builtin-fetch
Date: Thu, 12 Jul 2007 02:44:36 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707120244200.4516@racer.site> (raw)
In-Reply-To: <Pine.LNX.4.64.0707112113460.6977@iabervon.org>
Hi,
On Wed, 11 Jul 2007, Daniel Barkalow wrote:
> This series is the rest of builtin-fetch. It should probably not be used
> without a "[PATCH 3.5/4] Support bundles in transport fetch" which
> Johannes was going to write.
8-)
It is 3am, and I am already in the middle of git hacking, and should go to
bed, so that'll have to wait for tomorrow...
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-12 1:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 1:36 [PATCH 0/4] The rest of builtin-fetch Daniel Barkalow
2007-07-12 1:44 ` Johannes Schindelin [this message]
2007-07-12 1:49 ` Daniel Barkalow
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=Pine.LNX.4.64.0707120244200.4516@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--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.
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).