public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ChangeLog generation: Edit generated Changelogs
Date: Mon, 19 Sep 2011 19:09:46 +0200	[thread overview]
Message-ID: <20110919170946.GF1168@gentoo.org> (raw)
In-Reply-To: <4E7774CC.8010906@gentoo.org>

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

On 19-09-2011 19:58:52 +0300, Markos Chandras wrote:
> > What's the advantage of that?  We just end up with a different
> > location for the information that's now in a file called ChangeLog.
> > People want to be able to edit that stuff (yeah, no vote yet, but
> > the tendency seemed going that way) so why not keep it local to the
> > ebuild?
> Well it seems to me that most people want the simplest solution which
> is "if the changelog is wrong so be it"

That includes me, but that doesn't get us further. :)

> >> In this case you need smart filtering tools to avoid duplicate 
> >> messages ( one from $commit_message and the one you wrote
> >> yourself to fix that message ). However, this will be the case if
> >> we decide to allow edits on ChangeLogs.
> > 
> > Ehm.  Are we talking about the same thing here?  ChangeLog commits
> > don't end up in ChangeLogs, do they?
> What is a "Changelog commit"? How is that different from echangelog
> "Fix previous changelog entry" + repoman commit -m "Changelog Fixed".
> Could you please explain me the changelog edit mechanism you have in mind?

$EDITOR ChangeLog && repoman commit -m "added bugref"

(side-note: I don't see the point of your echangelog usage for this case)


-- 
Fabian Groffen
Gentoo on a different level

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

  reply	other threads:[~2011-09-19 17:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 14:08 [gentoo-project] ChangeLog generation: Edit generated Changelogs Markos Chandras
2011-09-16 21:32 ` "Paweł Hajdan, Jr."
2011-09-17  8:32   ` Markos Chandras
2011-09-17  9:07     ` Nirbheek Chauhan
2011-09-17 14:01       ` Rich Freeman
2011-09-19 13:26         ` Fabian Groffen
2011-09-19 13:44           ` Markos Chandras
2011-09-19 14:27             ` Fabian Groffen
2011-09-19 16:28               ` Markos Chandras
2011-09-19 16:51                 ` Fabian Groffen
2011-09-19 16:58                   ` Markos Chandras
2011-09-19 17:09                     ` Fabian Groffen [this message]
2011-09-19 17:21                       ` Markos Chandras
2011-09-19 17:53                         ` Fabian Groffen
2011-09-19 21:39               ` Donnie Berkholz
2011-09-19 21:46                 ` Michał Górny
2011-09-20  6:57                   ` Fabian Groffen
2011-09-28 17:37 ` Fabian Groffen
2011-09-28 18:24   ` Mr. Aaron W. Swenson
2011-09-29 17:04   ` Markos Chandras

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=20110919170946.GF1168@gentoo.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-project@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