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: Wed, 28 Sep 2011 19:37:26 +0200	[thread overview]
Message-ID: <20110928173726.GC704@gentoo.org> (raw)
In-Reply-To: <4E735841.9070209@gentoo.org>

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

On 16-09-2011 17:08:01 +0300, Markos Chandras wrote:
> Council decided to push back to ML the remaining bullet point about
> ChangeLog generation[1]

I propose that the council reconsiders their answers to all of the
questions, in particular the most important one "do we want ChangeLogs
to be auto-generated".

I propose instead that the council votes on NOT auto-generating
ChangeLogs, but instead asks the Portage team to implement updating the
ChangeLog file as part of repoman commit when there are files modified
(includes removal) excluding the ChangeLog file itself.

This solves most problems raised by council members, as well as others on
the various threads on this topic.
- The file can be edited (council intentional vote)
- All existing information is retained (council vote)
- Repoman updates ChangeLog so no filtering voodoo (council vote)
- Works with AnyVCS and branches*
- Needs no changes regarding Manifests, since ChangeLog is just in
  AnyVCS, known to repoman during commit


* assuming the merger either uses plain commit before finally merging
  the changes to the final tree (and committing with repoman commit
  ther), or the merger simply resolves the conflict by discarding
  changelog changes and performing final repoman commit with a full message

-- 
Fabian Groffen
Gentoo on a different level

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

  parent reply	other threads:[~2011-09-28 17:37 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
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 [this message]
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=20110928173726.GC704@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