From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ChangeLog generation: Edit generated Changelogs
Date: Sat, 17 Sep 2011 11:32:01 +0300 [thread overview]
Message-ID: <4E745B01.9040805@gentoo.org> (raw)
In-Reply-To: <4E73C08B.9030801@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 09/17/11 00:32, "Paweł Hajdan, Jr." wrote:
> On 9/16/11 7:08 AM, Markos Chandras wrote:
>> Council decided to push back to ML the remaining bullet point
>> about ChangeLog generation[1]
>>
>> "should we require that autogenerated changelogs have a way to
>> edit them afterwards to fix typos and such."
>
> In my opinion we should do the simplest thing that works, because
> bikeshedding on this is already taking too long.
>
> There are many successful open source projects which do not have
> explicit ChangeLog files and rely only on VCS logs. They're doing
> fine.
>
> I agree that there may be benefits to handling the ChangeLogs in
> some fancy way, but let's be practical and pragmatic. In my opinion
> it's a minor issue, and benefits of git migration would be far
> greater.
>
> Paweł
>
In my opinion, we do not need to care about typos etc. We are human
beings, so mistakes are part of our lives. Being able to fix
post-generated changelogs will increase the size of $VCS since
Changelogs need to be placed to $VCS for editing after generation and
having a smart deduplication algorithm on the server side to filter
duplicate messages. This is a bit stupid. If you make a mistake on
your commit message, that's fine. Be careful next time.
- --
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iQIcBAEBCgAGBQJOdFsBAAoJEPqDWhW0r/LC1yAP/RpRGFGjoXwEZIjtDpI6Tx3A
yjD+KWLvgRR/UliI0NpBsc+OTPY3coF3dill+9q1G3LaZiwpBr2w18GXZCR9uJZ3
TuI2nPMIkRtYzH60ykRKXYcGqwC9RJWIz1kZdlfG7ych5OxuyXLkmxP/FSVRf63P
PZe/MFCm9PeVLhv05jDoSqimjvh23RfQ9Cq1OrujHD2fTDzS6V/wNRDXFZlX40bU
XCh+tWjkwsiPaWVZ79ttdgS0IlVPReBIyQpL8Es8o853vuhGNmftOg3yqynXLYZA
tMCi3T1+W6ZpwKAM6rSj+2NegydDELt9UQThlhFEU63Nd+wAIGIOxnXPHx/w7a1p
JMhrhqhxaZBziGSHQAaUQVIy8I+23hIA8W7f1d9NbePwsjOS4ZWUYQe7Ni1AJjWL
e4o138FyBjip8dGFhjAdg23f2CIRQwO9ySlAwpXbQjWSMUCLY7LN8dNVmEJrCtBL
LCg3XtQ8PIXH/PHwNrSfR5YnsQRR2SgFrWLa+e6kVHS66NQ+/iSLOK/6LXapVJpg
EYQy4kyCKq66rxE2EkbrmoVdz/ozdzTatRPRhOcU1ApEb16qKXY7c8fkjw3mnjgT
f7QyxYyvrTO2xPdqyFV+psnD8E/cqzHJ6dCPrdbDzzgKhBLspEOYSoiX3e8POm2K
Tr2l5KKkSi576I9oiUr/
=rN9F
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-09-17 8:34 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 [this message]
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
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=4E745B01.9040805@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