From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2nd try] Make git-fmt-merge-msg a builtin
Date: Tue, 04 Jul 2006 00:56:35 -0700 [thread overview]
Message-ID: <7vk66tls5o.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0607040948170.29667@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Tue, 4 Jul 2006 09:50:37 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> I should have put PATH/RFC. I did not want to remove the script right
> away, so people could compare outputs (like Martin did with
> git-format-patch).
Well the stuff is quite straightforward and I think we could fix
it in-tree while in "next".
>> I think we should extend boolean to accept 'yes' and 'no',
>
> In that case, could we have "YesPlease", "oui", "si" and "da", too? ;-)
Hai? Nah, that's too much.
next prev parent reply other threads:[~2006-07-04 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 15:18 [PATCH 2nd try] Make git-fmt-merge-msg a builtin Johannes Schindelin
2006-07-03 22:39 ` Junio C Hamano
2006-07-04 7:50 ` Johannes Schindelin
2006-07-04 7:56 ` Junio C Hamano [this message]
2006-07-04 8:18 ` Johannes Schindelin
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=7vk66tls5o.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--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