From: Sean <seanlkml@sympatico.ca>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] ls-remote fix for rsync:// transport
Date: Thu, 25 May 2006 01:01:25 -0400 [thread overview]
Message-ID: <BAYC1-PASMTP073667D87F8BC653B62894AE990@CEZ.ICE> (raw)
Message-ID: <20060525010125.e2d6325d.seanlkml@sympatico.ca> (raw)
In-Reply-To: <7v7j4a3f9i.fsf@assigned-by-dhcp.cox.net>
On Wed, 24 May 2006 21:22:17 -0700
Junio C Hamano <junkio@cox.net> wrote:
> I think this would fix the "cloning rsync:// clones repository fine but
> does not check out the working tree" problem.
Nice find, works here.
Sean
prev parent reply other threads:[~2006-05-25 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 4:22 [PATCH] ls-remote fix for rsync:// transport Junio C Hamano
[not found] ` <20060525010125.e2d6325d.seanlkml@sympatico.ca>
2006-05-25 5:01 ` Sean [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=BAYC1-PASMTP073667D87F8BC653B62894AE990@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--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