From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Markus Heidelberg" <markus.heidelberg@web.de>,
"Santi Béjar" <santi@agolina.net>,
"Nguyễn Thái Ngọc" <pclouds@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 1/2] init: support --import to add all files and commit right after init
Date: Fri, 27 Mar 2009 01:08:28 -0400 [thread overview]
Message-ID: <20090327050828.GA23568@coredump.intra.peff.net> (raw)
In-Reply-To: <20090327050626.GA23512@coredump.intra.peff.net>
On Fri, Mar 27, 2009 at 01:06:26AM -0400, Jeff King wrote:
> Another option would be a patch on top of the original to allow
>
> git config --global init.importmessage 'Commit inicial'
>
> or
>
> git config --global init.importeditor true
>
> I have no interest in writing such a patch, but I don't see a reason to
> reject it.
Actually, there is one possible reason to reject it: scripts could not
rely on the behavior of "--import" without it. But I think it is OK to
make a conscious decision that this is a feature for _humans_, and that
scripts can use "init && add && commit" (or they can be happy with
dealing with the human's choice of editor or not).
-Peff
next prev parent reply other threads:[~2009-03-27 5:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 10:58 [PATCH 1/2] init: support --import to add all files and commit right after init Nguyễn Thái Ngọc Duy
2009-03-25 11:35 ` Jeff King
2009-03-25 22:54 ` Nguyen Thai Ngoc Duy
2009-03-25 11:56 ` Santi Béjar
2009-03-25 12:38 ` Johannes Schindelin
2009-03-25 12:42 ` Jeff King
2009-03-25 12:49 ` Santi Béjar
2009-03-26 21:23 ` Markus Heidelberg
2009-03-27 2:03 ` Johannes Schindelin
2009-03-27 5:06 ` Jeff King
2009-03-27 5:08 ` Jeff King [this message]
2009-03-28 10:58 ` Markus Heidelberg
2009-03-28 12:39 ` Johannes Schindelin
2009-03-28 13:09 ` Markus Heidelberg
-- strict thread matches above, loose matches on Subject: below --
2009-03-26 10:10 Nguyễn Thái Ngọc Duy
2009-03-26 10:13 ` Jeff King
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=20090327050828.GA23568@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=markus.heidelberg@web.de \
--cc=pclouds@gmail.com \
--cc=santi@agolina.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;
as well as URLs for NNTP newsgroup(s).