From: John Rood <mr.john.rood@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stefan Beller <sbeller@google.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: feature request
Date: Thu, 27 Oct 2016 18:16:50 -0500 [thread overview]
Message-ID: <CALj-rGfa5qWHiR42ggN3nWS56SGKHbcLttcyO-zLsSY6BfFifQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqshrh4d91.fsf@gitster.mtv.corp.google.com>
Thanks. I wasn't aware of --no-edit, but that is indeed exactly what I
was looking for.
I think your point about encouraging users to make good use of commit
messages is good.
My concern though is that vim isn't encouraging users to leave good
messages as much as it is scaring them away from leaving messages at
all.
On Thu, Oct 27, 2016 at 5:51 PM, Junio C Hamano <gitster@pobox.com> wrote:
> John Rood <mr.john.rood@gmail.com> writes:
>
> [administrivia: do not top post]
>
>> What I'm really seeking is not a make-shift solution for myself, but
>> an intuitive solution for the novice user-base at large.
>
> Well, there are -m and --no-edit. Recording commits with useless
> single liner is a bad habit to get into, and change to encourage
> novice user-base at large to do so is not a good idea.
next prev parent reply other threads:[~2016-10-27 23:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 21:55 feature request John Rood
2016-10-27 22:01 ` Stefan Beller
2016-10-27 22:05 ` John Rood
2016-10-27 22:24 ` John Rood
2016-10-27 22:27 ` Junio C Hamano
2016-10-27 22:48 ` John Rood
2016-10-27 22:51 ` Junio C Hamano
2016-10-27 23:16 ` John Rood [this message]
2016-10-27 22:30 ` Stefan Beller
2016-10-27 22:44 ` John Rood
2016-10-27 22:46 ` Junio C Hamano
2016-10-27 23:24 ` David Lang
2016-10-28 8:49 ` Johannes Schindelin
2016-10-28 12:54 ` Philip Oakley
-- strict thread matches above, loose matches on Subject: below --
2024-06-20 12:58 Feature Request Clement Sello Tsetsa
2024-06-20 13:29 ` rsbecker
2013-02-18 18:52 feature request Jay Townsend
2013-02-18 19:54 ` James Nylen
2013-02-18 20:45 ` Jeff King
2013-02-19 3:26 ` Drew Northup
2013-02-19 22:27 ` Shawn Pearce
2012-10-16 11:36 Angelo Borsotti
2012-10-16 12:15 ` Andrew Ardill
2012-10-16 17:27 ` Angelo Borsotti
2012-10-16 23:30 ` Sitaram Chamarty
2012-10-17 0:00 ` Andrew Ardill
2012-10-16 13:34 ` Christian Thaeter
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=CALj-rGfa5qWHiR42ggN3nWS56SGKHbcLttcyO-zLsSY6BfFifQ@mail.gmail.com \
--to=mr.john.rood@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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 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).