public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proper commit messages
Date: Tue, 9 Aug 2005 13:47:36 +0100	[thread overview]
Message-ID: <20050809134736.0f21dbf7@snowdrop.home> (raw)
In-Reply-To: <20050809122320.GD31594@unixforces.net>

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

On Tue, 9 Aug 2005 12:23:20 +0000 Markus Rothe <corsair@gentoo.org>
wrote:
| Stephen Bennett wrote:
| > On Tue, 9 Aug 2005 11:36:18 +0000
| > Markus Rothe <corsair@gentoo.org> wrote:
| > 
| > > Personaly I find it a little bit annoying to write changes twise.
| > > One time in Changelog and one time in --commitmsg. How about
| > > using the commitmsg for Changelog as default, but if a Changelog
| > > entry already exists, then write nothing to Changelog.
| > 
| > I'm sure you can manage to write a bash function to call echangelog
| > and repoman commit with the same message.
| 
| Sure, I can and the other mail shows that it is *realy* simple, but
| why should every dev write his own "script", when this could be done
| once for all?

Isn't this one of those things that's best done on a per-dev basis?
It's so trivial there's no point shipping an app that does it --
reading the associated documentation would take longer than writing
your own. Plus that way you can incorporate personalised clever things
such as auto keyword messages for arch teams

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-09 12:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 20:44 [gentoo-dev] Proper commit messages Ciaran McCreesh
2005-08-09 11:36 ` Markus Rothe
2005-08-09 11:55   ` Simon Stelling
2005-08-09 12:40     ` Diego 'Flameeyes' Pettenò
2005-08-09 12:04   ` Stephen Bennett
2005-08-09 12:23     ` Markus Rothe
2005-08-09 12:47       ` Ciaran McCreesh [this message]
2005-08-09 12:59         ` Markus Rothe
2005-08-09 19:07         ` Jonathan Smith
2005-08-09 19:22           ` Ciaran McCreesh
2005-08-09 20:56             ` Henrik Brix Andersen
2005-08-09 22:54             ` Tuan Van
2005-08-09 23:31               ` [gentoo-dev] " Arnaud Launay
2005-08-09 23:38                 ` LostSon
2005-08-09 23:40                 ` Ciaran McCreesh
2005-08-09 23:48                   ` Mike Frysinger
2005-08-10  8:03                     ` Alin Nastac
2005-08-10 21:46                       ` Dice R. Random
2005-08-11 16:16                     ` Drake Wyrm
2005-08-09 23:47                 ` Mike Frysinger
2005-08-15 14:03   ` [gentoo-dev] " Aron Griffis

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=20050809134736.0f21dbf7@snowdrop.home \
    --to=ciaranm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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