From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ChangeLog generation: Edit generated Changelogs
Date: Mon, 19 Sep 2011 16:44:51 +0300 [thread overview]
Message-ID: <4E774753.7020303@gentoo.org> (raw)
In-Reply-To: <20110919132655.GA1168@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 09/19/11 16:26, Fabian Groffen wrote:
> I would prefer going this route myself. Generate all ChangeLogs
> from commit messages only. This is easy to implement (POC is
> running for Prefix), but has a little issue with ChangeLog being in
> Manifest file. I think we should just omit it, or (better) allow
> the Manifest to have multiple signed parts, such that the ebuilds,
> dists and files are signed by the committing developer, and the
> ChangeLog is signed by the generation process (like snapshots
> are).
If you generate Changelogs from commit messages then you dont need to
place the to $VCS unless you want to edit them ( see below )
>
> The council has, however, (like Markos' initial mail explained)
> decided that ChangeLog entries must be updatable (e.g. corrected)
> afterwards.
Really? when? There is no decision on this topic yet[1](3rd bullet
point). If I am wrong, please point me to the correct source. I
thought this discussion is about whether we want to edit them
afterwards or not. So unless we decide to edit them, we don't need
ChangeLog files
[1]http://www.gentoo.org/proj/en/council/meeting-logs/20110809-summary.txt
- --
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iQIcBAEBCgAGBQJOd0dTAAoJEPqDWhW0r/LC7wgP/RCQG3dFHYLv3EIsnEakiw+x
i0wbXROOsQYhd1MHPw6LEu7sKHIoTOvHuk2JpWp2VzUHrusuzTtMhGgxBc1gS7oj
5Q/npe8rBYZOBwrSgVLpAKFOaNhM6UrHVDmGudC+y5c4AjlwSZzLFBaCSJT1ihBb
Q0M24Pipng6/ppPUUa3rZHR4GPY0+6gC9gNixn40M1/WxtxchqSc2k4FCvWh5+Nr
UC4LUGKTZR+Ik/ndJQ+cVX24xYBOOXVrXsKfVKNtiOUW+AXeewHCBuGrSh2UnLdD
hWXwvF0imCVsHGzbpAV2eS0cu7sIx+uNj0Y+ajFQZbmP0LINhRwxlecxzu//I0ww
ha9gZpwcrC4S8F2sP1Er1uZQfBZazLK+0TzqKXYm0hqmamEXR0C99YZOZHn+mu8h
NGTdIWc8siv9Di0SA/FechYBYNi30c8ttQ740lkp9Wqg3jqm7yfihxASqLqXZK5l
JjLFuJteLzrDqXA6yO8LhLiwd9C8LIpHr1qsVHTimLDGqHlZGUxo9KgcLqbxQQAJ
hYvPo3IReLRKWZrea2vZKZI8453GzucgOjV9OGjF2NcOm1AL10cVIRmyPb5KEhqo
Ati1gjWprGmPsVrvYqEl3FlC8sE25dqjEvoSQFlTM4UqflQRTmxroNHSZu1cv1FY
rH2rsRRuqug8NPCA32Ou
=YDM2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-09-19 13:46 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 [this message]
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
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=4E774753.7020303@gentoo.org \
--to=hwoarang@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