> I think that sort of metadata is more appropriate for an RT ticket. A
> commit messages should describe primarily * what* is being changed
> instead of *why* the change is being made. Of course, including the
> *why* doesn't hurt but I don't believe it should be part of our
> guidelines.
(Th
On Tue, Dec 20, 2005 at 11:56:17PM +0100, Leopold Toetsch wrote:
> I've tried that mentioned svn2cl util for the 50 last revs. Due to file
> moves or other global changes a lot of the created ChangeLog entries
> are a meaningless mess of a list of filenames + an "oneliner". If I
> need this I ca
On Tue, Dec 20, 2005 at 07:45:30AM -0800, jerry gay wrote:
> On 12/20/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> > In it's current form ChangeLog is little more than a pointer to NEWS.
> > This is really defeating the purpose of what ChangeLog is supposed to
> > contain; detailed information a
On Dec 20, 2005, at 16:45, jerry gay wrote:
... automatic generation sounds great, but it's no good
without clear commit messages. one or two word commit messages should
be shunned in favor of brief yet clear descriptions of the change,
including which parrot components are affected.
here are
On 12/20/05, Joshua Hoblitt <[EMAIL PROTECTED]> wrote:
> In it's current form ChangeLog is little more than a pointer to NEWS.
> This is really defeating the purpose of what ChangeLog is supposed to
> contain; detailed information about changes. It is also more or less
> redundant with the functio
Anything that makes it easier for developers to develop is a good thing.
On Dec 20, 2005, at 7:40 AM, Nicholas Clark wrote:
On Tue, Dec 20, 2005 at 02:03:44AM -1000, Joshua Hoblitt wrote:
people start adding detailed information to ChangeLog. I think it is
entirely reasonable to machine gene
On Tue, Dec 20, 2005 at 02:03:44AM -1000, Joshua Hoblitt wrote:
> people start adding detailed information to ChangeLog. I think it is
> entirely reasonable to machine generate this file with svn2cl[1] before
> each release. Comments?
Generating it from the subversion commit messages seems a go
In it's current form ChangeLog is little more than a pointer to NEWS.
This is really defeating the purpose of what ChangeLog is supposed to
contain; detailed information about changes. It is also more or less
redundant with the function of NEWS. However, I am not proposing that
people start addin
