From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 0/5] Shallow clone fixes
Date: Fri, 24 Nov 2006 16:43:47 +0100 [thread overview]
Message-ID: <ek73sd$v0p$1@sea.gmane.org> (raw)
In-Reply-To: 8764d4vqno.fsf@wine.dyndns.org
Alexandre Julliard wrote:
> This series fixes a number of small problems in the shallow clone
> support in pu. After that it seems to work fairly well for me.
Could you make the rest of patches in series be reply to (directly or
indirectly) to the introductory message? Thanks in advance.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2006-11-24 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 14:57 [PATCH 0/5] Shallow clone fixes Alexandre Julliard
2006-11-24 15:43 ` Jakub Narebski [this message]
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='ek73sd$v0p$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).