From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Karl Hasselström" <kha@treskal.com>,
"Martin Langhoff" <martin@catalyst.net.nz>,
"Matthias Urlichs" <smurf@smurf.noris.de>,
"Herbert Valerio Riedel" <hvr@gnu.org>,
git@vger.kernel.org
Subject: Re: [PATCH] git-svnimport symlink support
Date: Wed, 19 Apr 2006 12:16:02 +1200 [thread overview]
Message-ID: <46a038f90604181716t3d04ec95u92401858736fa6dc@mail.gmail.com> (raw)
In-Reply-To: <7v3bgcngqc.fsf@assigned-by-dhcp.cox.net>
On 4/18/06, Junio C Hamano <junkio@cox.net> wrote:
> Karl, Martin, Smurf, Comments?
+1 but bear in mind that I am not learned in the ways of the SVN specials...
martin
next prev parent reply other threads:[~2006-04-19 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1FVRRH-0003Wz-6w@fencepost.gnu.org>
2006-04-17 19:29 ` [PATCH] git-svnimport symlink support Junio C Hamano
2006-04-18 9:11 ` smurf
2006-04-19 0:16 ` Martin Langhoff [this message]
2006-04-20 6:15 ` smurf
2006-04-20 6:54 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46a038f90604181716t3d04ec95u92401858736fa6dc@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=hvr@gnu.org \
--cc=junkio@cox.net \
--cc=kha@treskal.com \
--cc=martin@catalyst.net.nz \
--cc=smurf@smurf.noris.de \
/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).