Re: [Fink-devel] Merge fink ChangeLogs?

[Chris Z. <be...@ma...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 29, 2006, at 8:01 AM, Max Horn wrote:

> Hence, I am wondering whether we should merge all those ChangeLogs  
> (21) and only keep a single one... This would involved changing  
> entries like
> 2001-05-08  Christoph Pfisterer  <cp...@ch...>
>
> 	* config.guess, config.sub: Updated with latest version
> 	(2001-04-20) from ftp.gnu.org.
>
> such that they list the full file path, i.e. "update/config.guess,  
> update/config.sub" in this case. And of course removing duplicate  
> entries etc., in short, a lot of manual work.
>
> Clearly, this would be a *lot* of work for perlmod/Fink/ChangeLog  
> which is by far the biggest. All the others are fairly short. My  
> suggestion hence would be to start out by merging all ChangeLogs  
> *except* for perlmod/Fink/ChangeLog into a single one (this should  
> be relatively quickly done, and I would do it). While not quite  
> "perfect", this would mean that at least there are only two,  
> instead of 21, ChangeLog files to watch & update. Merging "perlmod/ 
> Fink/ChangeLog" then could be done at a later point, or gradually,  
> or with a clever script, or by hiring some slaves, or so ;-).
>
>
> What do you think? Is this idea bogus?

No, it's a good idea, many times i edit one changelog, and forget to  
edit the 2nd. If you would be willing to start, I will help when I  
can. It would be hard to coordinate, but maybe when someone starts to  
play w/the changelog they commit their name at the end of the file,  
then when they are done playing, remove their name. This way we don't  
get multiple people working on it, and lots of conflicts. Also make  
sure people only use the main ChangeLog from now on.

- -chris zubrzycki
- - --
PGP public key: http://homepage.mac.com/beren/publickey.txt
ID: 0xA2ABC070
Fingerprint: 26B0 BA6B A409 FA83 42B3  1688 FBF9 8232 A2AB C070
_________________________________________________
This message is encoded using the Rot-26 encoding method.   
Unauthorized decoding of this message may result in extreme penalties  
under the DMCA.  These penalties include, but are not limited to: US 
$100,000 fine, life imprisonment, castration, death, limp hair,  
terminal halitosis, and amputation of the extremities.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)
Comment: Please sign reply-http://www.gnupg.org

iEYEARECAAYFAkQqnRcACgkQ+/mCMqKrwHAgAACgjm+OpwwnXQFHwZHY+/YaRO/V
kFoAn2hbJ+GNMQ0KBQj2aExWBh0xUeGt
=eoJB
-----END PGP SIGNATURE-----