From: "Santi Béjar" <santi@agolina.net>
To: Jeff King <peff@peff.net>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"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: Wed, 25 Mar 2009 13:49:40 +0100 [thread overview]
Message-ID: <adf1fd3d0903250549l60e4a2d1j8bd57ba66d24a678@mail.gmail.com> (raw)
In-Reply-To: <20090325124219.GA5307@coredump.intra.peff.net>
2009/3/25 Jeff King <peff@peff.net>:
> On Wed, Mar 25, 2009 at 01:38:30PM +0100, Johannes Schindelin wrote:
>
>> > > +If no message is given, "Initial commit" will be used.
>> >
>> > Why a default message and not running the editor?
>>
>> Because I would say "Initial commit" anyway.
And I would say "Commit inicial".
>
> Agreed. This feature is about convenience.
... for project in english.
> If you really want to say
> something more exciting, then use "git commit" directly. Heck, you can
> even "git commit --amend" it afterwards.
I can. But then it is no longer "convenience".
But anyway, it is like the "Merge branch..." commit message for
merges. So nothing new.
Santi
next prev parent reply other threads:[~2009-03-25 12:51 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 [this message]
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
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=adf1fd3d0903250549l60e4a2d1j8bd57ba66d24a678@mail.gmail.com \
--to=santi@agolina.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.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).