From: Chris Packham <judge.packham@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [RFC] Disabling status hints in COMMIT_EDITMSG
Date: Wed, 11 Sep 2013 09:11:29 +1200 [thread overview]
Message-ID: <CAFOYHZBiMNMeq4JKX1st0yTLJ8hm8aUNGPd0WA2uaLhOP44w6w@mail.gmail.com> (raw)
In-Reply-To: <vpqtxhtey4t.fsf@anie.imag.fr>
On Tue, Sep 10, 2013 at 11:04 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Chris Packham <judge.packham@gmail.com> writes:
>
>> On 10/09/13 21:19, Matthieu Moy wrote:
>>> Hi,
>>>
>>> I just noticed that the template COMMIT_EDITMSG was containing status
>>> hints, and that they were not particularty helpfull _during_ a commit. I
>>> think it would be sensible to ignore advice.statusHints and disable
>>> hints unconditionally when writting to COMMIT_EDITMSG.
>>>
>>> Any objection?
>>>
>>
>> I did recently find them useful/reassuring when I was committing a
>> merge. But I wouldn't consider that a strong objection.
>
> Just to make sure we're talking about the same thing: when commiting a
> merge, the template currently looks like:
>
> Merge branch 'master' of /tmp/git
>
> Conflicts:
> foo.txt
> #
> # It looks like you may be committing a merge.
> # If this is not correct, please remove the file
> # .git/MERGE_HEAD
> # and try again.
>
>
> # Please enter the commit message for your changes. Lines starting
> # with '#' will be ignored, and an empty message aborts the commit.
> # On branch master
> # Your branch and 'origin/master' have diverged,
> # and have 3 and 1 different commit each, respectively.
> # (use "git pull" to merge the remote branch into yours)
> #
> # All conflicts fixed but you are still merging.
> # (use "git commit" to conclude merge)
> #
> # Changes to be committed:
> #
> # modified: foo.txt
> #
>
> What I'd like to remove are the parts between parenthesis :
>
> (use "git commit" to conclude merge)
> (use "git pull" to merge the remote branch into yours)
>
> The first part (It looks like [...]) would remain, of course.
>
> Actually, even the "All conflicts fixed but you are still merging." part
> is not really accurate when the commit is already started.
OK. I wouldn't miss that parts in parenthesis. If I chose to abort the
commit from the editor (e.g. :cq in vi) git status would still tell me
what I need to know.
>
> --
> Matthieu Moy
> http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-09-10 21:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 9:19 [RFC] Disabling status hints in COMMIT_EDITMSG Matthieu Moy
2013-09-10 9:53 ` Chris Packham
2013-09-10 11:04 ` Matthieu Moy
2013-09-10 21:11 ` Chris Packham [this message]
2013-09-10 16:42 ` Junio C Hamano
2013-09-11 7:24 ` Matthieu Moy
2013-09-11 7:42 ` Javier Domingo
2013-09-11 8:05 ` Matthieu Moy
2013-09-11 9:14 ` John Szakmeister
2013-09-11 14:03 ` Javier Domingo
2013-09-11 17:24 ` Junio C Hamano
2013-09-11 17:40 ` Matthieu Moy
2013-09-10 18:03 ` Jonathan Nieder
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=CAFOYHZBiMNMeq4JKX1st0yTLJ8hm8aUNGPd0WA2uaLhOP44w6w@mail.gmail.com \
--to=judge.packham@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--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;
as well as URLs for NNTP newsgroup(s).