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 19:58:52 +0300 [thread overview]
Message-ID: <4E7774CC.8010906@gentoo.org> (raw)
In-Reply-To: <20110919165152.GD1168@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 09/19/11 19:51, Fabian Groffen wrote:
>>
>> Yes a file is needed but like I said before, this file can be
>> generated on a post-commit server just before populating portage
>> to rsync servers
>
> 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"
>
>>> An additional advantage of keeping the file is that we can
>>> easily fix all entries that people wrote/committed ugly and
>>> helpless messages for, like "^" and so on.
>>>
>> 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?
- --
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iQIcBAEBCgAGBQJOd3TMAAoJEPqDWhW0r/LCNaoP+wUE5u5wxey16ZJ92iNKPFVh
fNeuLJx2KlRRBnEw4iWLg4K0radgK+QqTJnp3FKqqyLdkDBtzjmMO52+aUeTb8LU
hwPkwi9UnshbWRNl3sOdrXH/bL+jCFuqxFCaM9pOhzQT5WwzjDkNVVry9VZKAjOM
I125/sHha4asZzl6AxcvTMtd3pn4eUNYySs2Qg5QLQZBNR6EougbDz5U386uPAYW
S8an8gPDABEg3BfiAxGKBz4vssNuFSOmwtmDAZP0O5QAzfV9exm9YAERQYmPpLt2
mUYRpxDRqEd3Swzk0RgRXu0Hc/yzqJDD7Zv05OnVq6KKkxRAF9SnMY2888jNObhn
0FLSFs61b1DfkSUdOBqTvJyCPdNe/y1JZ/tIdJjUUAnokXtL8uGxoruyHG+dxPuE
OcCuS1Z3NmLdyGl2X/fI8BhXdH2HRRPHdUypddxjtBeBMYolLVX5gYdkoLK6yeBK
BeokfJF8bGNE4j89/+nLtldlU0AEza6c35v+tlGou4kLXBDwnLYmvlJkGfzNxb75
eLp5qbAL564M1W4rtZ3RWCZVhzWdXMMONO0qHc5d+/umLVdJy6We1DGOF/fuYaPg
ETNspIE1unCFMthD8Iz464iNw8N4Dh2Rq3mv6Ammwe1L9uKbA2pUxIT7fDJAi0bV
GwQwEYxeW82hKhH0WcHu
=uB0y
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-09-19 17:02 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 [this message]
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=4E7774CC.8010906@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