git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Doyle <wpdster@gmail.com>
To: git <git@vger.kernel.org>
Subject: How to "pre-populate" a git message
Date: Fri, 3 Dec 2010 12:51:52 -0500	[thread overview]
Message-ID: <AANLkTim=dVxVLL31aEBrjw7OhXpdYOjAO9Sk16gGP3zJ@mail.gmail.com> (raw)

Once in a while, I would like to run some scripts that will
automatically generate some files that I keep maintained in my
repository.  (Yes, I know that I shouldn't have to keep them version
controlled if I can regenerate them, but it's easier to check out old
versions of the files than it is to check out old versions of the
repository, wait 1/2 hour to regenerate the files, and then look at
them).

I also like to review the files before they get committed.

Is there any way I can "pre-populate" the commit message so that I can
run my "regenerate" command, review the differences, and then commit
the changes with my prewritten message?

--wpd

             reply	other threads:[~2010-12-03 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 17:51 Patrick Doyle [this message]
2010-12-03 19:29 ` How to "pre-populate" a git message Jonathan Nieder
2010-12-03 19:36 ` Dirk Süsserott

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='AANLkTim=dVxVLL31aEBrjw7OhXpdYOjAO9Sk16gGP3zJ@mail.gmail.com' \
    --to=wpdster@gmail.com \
    --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).