From: Junio C Hamano <junkio@cox.net>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Kevin Geiss <kevin@desertsol.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/1] git-cvsexportcommit.perl: Fix usage() output.
Date: Mon, 14 Nov 2005 15:04:52 -0800 [thread overview]
Message-ID: <7vsltyvnjf.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <46a038f90511141420u11e396d3q9a6710c79abe0ca3@mail.gmail.com> (Martin Langhoff's message of "Tue, 15 Nov 2005 11:20:59 +1300")
Martin Langhoff <martin.langhoff@gmail.com> writes:
> ... I'm happy with Kevin's patches -- what's the ideal
> workflow for this? Is the sign-off line important enough that
> I should setup a public repo for you to pull from?
Given that you are far more familiar with that part of the code,
and I suspect I'd be asking your help in archimport as well, a
repo I can pull from would be more preferable (and sign-off by
you is certainly an added bonus). If a public repo is too much
hassle, however, e-mail forwarding is perfectly fine as well.
Your choice.
BTW, there is no "mana" points involved in deciding if I
directly pull from somewhere. Even if that were the case, you
have accumulated enough of them already ;-).
> BTW, File::Basename is a standard library usually installed w perl --
> it shouldn't add any painful dependencies. Not sure if that matters.
Although some might find "${\function}" expansion too cute for
their taste, Keven's code is fine as-is for me. I launched the
baloon just wanting to see what others have to say ;-).
next prev parent reply other threads:[~2005-11-14 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 16:40 eth Kevin Geiss
2005-11-14 16:45 ` [PATCH 1/1] git-cvsexportcommit.perl: Fix usage() output Kevin Geiss
2005-11-14 20:24 ` Kevin Geiss
2005-11-14 22:14 ` Junio C Hamano
2005-11-14 22:20 ` Martin Langhoff
2005-11-14 23:04 ` Junio C Hamano [this message]
2005-11-15 5:10 ` Martin Langhoff
2005-11-14 16:47 ` eth Kevin Geiss
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=7vsltyvnjf.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=kevin@desertsol.com \
--cc=martin.langhoff@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.