On Wed, Feb 02, 2011 at 09:59:02AM +0100, Julien Palard wrote: > Hi Salvatore > > On Wed, Feb 2, 2011 at 9:09 AM, Salvatore Bonaccorso <email@example.com> wrote: > >> Hum I have to put the changlog in the git repository ? It's a bit > >> tricky as git have its own changelog system to maintain a manual > >> changelog file in it ? Whatever, it's done, and i removed the .po in > >> the tarball. > > > > Hmm, well the point mostly of upstream changelog file is to see what > > changed (bugfixes, new features, ...) from versions x to y, but not > > having all git commits in it. > > Hum, so, I should also rewrite the CHANGELOG file to reflect only big > changes (now it's a `git log > CHANGELOG`) ? Erm, I believe that Salvatore might have made the same mistake that I did until recently - a bit unclear on the "changelog" and "news" files :) I've always thought that the purpose of the changelog would be to reflect bigger changes, but it would seem that the GNU Coding Standards do not agree - it seems you're doing the right thing with your CHANGELOG file, and the file that Salvatore is talking about ought to be named "NEWS". I've recently bowed to the majority's opinion and started renaming my ChangeLog files to NEWS in new upstream releases of software that I write. Of course, this excludes Perl modules / extensions, where the tradition still is to have the "news" in a file named "Changes" :) As Savatage sing, "Welcome to the system, here's the situation / It's a bit confusing, welcome to the maze!" :P G'luck, Peter -- Peter Pentchev firstname.lastname@example.org roam@FreeBSD.org email@example.com PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 I had to translate this sentence into English because I could not read the original Sanskrit.
Description: Digital signature