[Bash-completion-devel] Policy for CHANGES

[David Paleino]

Hello everybody,

I've seen that CHANGES is being "polluted" by non-upstream contributions,
usually coming from downstream bug trackers or mails to the list.

To avoid confusion about who accepted a patch (yes, we could use "git blame"
over CHANGES), and to avoid the proliferation of sections for single-time
contributors, I'd suggest the following syntax:

[ Upstream Name Surname ]
* Fix blbla, patch by ThirdParty Contributor (Alioth: #...)

instead of making sections for each contributor (s/patch by/thanks to/ if you
prefer)

Opinions?

David

-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://deb.li/dapal
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/bash-completion-devel/attachments/20110427/400675d4/attachment.pgp>