All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Daniel Thomas <drt24@srcf.ucam.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [GSoC Proposal/RFC] Rolling commit message writing
Date: Mon, 29 Mar 2010 22:05:08 -0500	[thread overview]
Message-ID: <20100330030508.GA2887@progeny.tock> (raw)
In-Reply-To: <32541b131003291331y3ae5ca23la33466d588c1b9e1@mail.gmail.com>

Hi,

Avery Pennarun wrote:

> Given these existing capabilities, is it still worth adding the
> feature you propose?

I think it might be, in some modified form.

Suppose I am working on a medium-sized change that for reasons of
bisectability or ontology has to be one commit.  In the middle of
working, I notice I needed to do something nonobvious.  Currently when
this happens, I get out a pad of paper and write it down, so I can be
sure to mention it in the commit message.

Wouldn’t it be nicer in such situations to be able to say git add
--commit-message or similar, open an editor, and write the note right
away?

In other words, it would be nice to have a file in .git that is

 - cleared on successful commit
 - automatically used to fill COMMIT_EDITMSG, like MERGE_MSG is

I suspect something like this can be achieved by the combination of
the commit.template configuration variable and a post-commit hook to
clear the file, but I haven’t tried it.

Regards,
Jonathan

  reply	other threads:[~2010-03-30  3:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 19:32 [GSoC Proposal/RFC] Rolling commit message writing Daniel Thomas
2010-03-29 20:31 ` Avery Pennarun
2010-03-30  3:05   ` Jonathan Nieder [this message]
2010-03-30  4:32     ` Avery Pennarun
2010-03-30  5:02       ` the careless committer and fear of commitment (rebase -i vs add -p) Jonathan Nieder
2010-03-30  6:14         ` Ramkumar Ramachandra
2010-03-30 17:27   ` [GSoC Proposal/RFC] Rolling commit message writing Jeff King
2010-03-30 22:34 Daniel Thomas

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=20100330030508.GA2887@progeny.tock \
    --to=jrnieder@gmail.com \
    --cc=apenwarr@gmail.com \
    --cc=drt24@srcf.ucam.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.