git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Wolfgang Denk <wd@denx.de>
Cc: Andreas Ericsson <ae@op5.se>, Petr Baudis <pasky@suse.cz>,
	git@vger.kernel.org
Subject: Re: cg-commit does not run pre-commit hook?
Date: Thu, 12 Oct 2006 09:59:24 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610120957460.3952@g5.osdl.org> (raw)
In-Reply-To: <20061012155444.27391353BDE@atlas.denx.de>



On Thu, 12 Oct 2006, Wolfgang Denk wrote:
> > 
> > git log
> 
> Sorry, this does not work, as I can access the  commit  message  only
> *after* the commit completed, and then it's too late to get it into a
> file that shall be included with the very same commit.

Why? That's just stupid.

If you want to have a ChangeLog file, it's _much_ better to just 
auto-generate it after the fact. When you cut a tar-file, just have the 
script autogenerate the changelog then and there. Why do it inside the 
SCM that keeps track of the data _anyway_.

> True, as long as you can work within the SCM. The changelog file  I'm
> talking  about is mostly for people who just work with exported trees
> (for example, when they download a tarball).

Right - but it's easy enough to add it to the tar-ball, so..

		Linus

  reply	other threads:[~2006-10-12 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 20:30 cg-commit does not run pre-commit hook? Wolfgang Denk
2006-10-12  1:15 ` Petr Baudis
2006-10-12 14:27   ` Wolfgang Denk
2006-10-12 14:42     ` Andreas Ericsson
2006-10-12 15:54       ` Wolfgang Denk
2006-10-12 16:59         ` Linus Torvalds [this message]
2006-10-12 17:20           ` Linus Torvalds
2006-10-12 17:02         ` Josef Weidendorfer

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=Pine.LNX.4.64.0610120957460.3952@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=wd@denx.de \
    /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).