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 20:21:51 +0300 [thread overview]
Message-ID: <4E777A2F.3050306@gentoo.org> (raw)
In-Reply-To: <20110919170946.GF1168@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 09/19/11 20:09, Fabian Groffen wrote:
>
> $EDITOR ChangeLog && repoman commit -m "added bugref"
>
> (side-note: I don't see the point of your echangelog usage for this
> case)
>
>
Ok pretty much what I said in my previous email. In this case you edit
the ChangeLog but the "added bugref" text will be appended to
Changelog instead of fixing your previous commit message. In my
opinion we have two options here
1) Ignore commit messages that only affect ChangeLogs. This requires
the ChangeLog entry to be kept on $VCS cause it is easier
OR
2) Remove the head -1 ChangeLog entry and insert the new one.
In both cases, the ChangeLogs need to be on $VCS
The only advantage for having the post-commit server generating the
ChangeLogs is the reduce $VCS size. I can't see any other advantages
whatsoever
- --
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iQIcBAEBCgAGBQJOd3ovAAoJEPqDWhW0r/LClyQP/RSUboKuJUaukTrArX3L2082
3p82YkUO1AjfxaTNzDG55FCdIVDjANMLQZ8jmeltY9/RHp4gQYFWu/YUQ+cJZBGx
eQJvrwu6b+zJW+La5tckNcAb0DzB1wDrVT/d/caJ0Nyq5Hr7eUwrTSRZzWjCJ75y
BNUtDJwfSvOiD1LydMaclzfAA0lS8GKugmnpyI0tutAeK4mHwqtDg67BiEZEMpJX
22yGCUNQS9L+lNam3XWRNsCKyrSR0Es8pSxqE8FYPenEkBwN/+s1AHKqTAp+6+kW
gWhqxdiVCHPE137sHoYVhdiNy/nyw2zkiL/hFrWuaismKeo+V/C3/MLKsjwaU9pz
uX7xvCNbDBEwsZ9nPZXBFpygUQV1n3lXC2AweXU3njC2G85mKIy1sUCdFn79g8C4
GcYu4DmZeo9M4OvPJytCPMjbnWYzoMguIjr2+EDOQ1zkImbEe4VzIsBbRhacXFOj
v91vbLadt2uKMAbfsMfKGeaBObk9WpUhUxrTcOZHha6pKVnmt0bCX7oboFfF5cHE
vu4w6ofUsamkVIJ5SK9MrhTZ1zpSy94pbqSkrIO5iU9debrdUtAv3SC3s8FA1JqJ
Q0WH2zkduuFf2hywheozLgdXwdGHotvyVzmRK60FH1e/aUz7PnhFHgSJBxhLW1eT
CQRWFxUUHMrRtATMPw7C
=Sw7T
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-09-19 17:23 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 [this message]
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=4E777A2F.3050306@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