git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Adam" <thomas.adam22@gmail.com>
To: git@vger.kernel.org
Subject: Template commit messages.
Date: Sun, 5 Aug 2007 13:32:48 +0100	[thread overview]
Message-ID: <18071eea0708050532x2d9bfddw96a9428f4840b1fc@mail.gmail.com> (raw)

Hello all,

Am I correct in thinking that the new template messages that will be
in the up and coming git release will alleviate an "annoyance" I've
currently got with commit messages?

Basically, I want a way of removing what is now, a long list of
untracked files from the commit message before it hits the editor --
I've looked at $GIT_DIR/.git/hooks/{pre,post}-commit as well as:
$GIT_DIR/.git/hooks/commit-msg in the hopes I could add  a sed command
there to remove the list of files, and whilst the sed command worked
fine on the command line, adding it to any of those files didn't.

Was this even the right approach?  I didn't want to go messing with
git-commit, frankly, so I am hoping that these new templates might
just do the trick.

You might ask why I've got such a large list of untracked files -- the
reason is because I use the same repository to build files in, which
themselves have no need to be added.  And whilst I can catch some of
these instances by using .gitignore, it's not enough since not all of
the files have a common extension or anything.  And whilst I realise
the list of untracked file is just a friendly warning to me, I find it
annoying and would rather it didn't appear at all if possible, since I
know myself which files need explicitly adding.  :)

Hope that makes sense, at least.  :)

Kindly,

Thomas Adam

             reply	other threads:[~2007-08-05 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 12:32 Thomas Adam [this message]
2007-08-08 16:24 ` Template commit messages Jan Hudec

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=18071eea0708050532x2d9bfddw96a9428f4840b1fc@mail.gmail.com \
    --to=thomas.adam22@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).