Re: [Evolution-hackers] Rebooting ChangeLog files in 3.x

2010-03-12 Thread Matthew Barnes
On Fri, 2010-03-12 at 07:26 +, Gilles Dartiguelongue wrote: > as long as it is not the, sadly common since git migration, raw git log > output, which is unreadable for downstream, then sure. Obviously it would be generated from git commit history. What type of formatting would you prefer? Be

Re: [Evolution-hackers] Rebooting ChangeLog files in 3.x

2010-03-11 Thread Gilles Dartiguelongue
> I'd like to clean this up in 3.0, so unless I hear objections, after > we > branch for GNOME 2.30 I'm going to remove all the ChangeLog* files in > the evolution, evolution-data-server, evolution-exchange, and gtkhtml > repositories [1] and replace them with a single top-level ChangeLog > placeh

[Evolution-hackers] Rebooting ChangeLog files in 3.x

2010-03-11 Thread Matthew Barnes
Now that we're using Git for source control, our ChangeLog files are redundant because the content is already available in Git's commit history. Worse, the change history we provide in release tarballs is partitioned across multiple ChangeLog files in the source tree, making it difficult to search