[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Abolishing ChangeLog files

From: Steve Youngs
Subject: Re: Abolishing ChangeLog files
Date: Fri, 29 Mar 2013 18:02:40 +1000
User-agent: Gnus/5.130006 (Ma Gnus v0.6) SXEmacs/22.1.15 (Goggomobil, linux)

* Richard Stallman <address@hidden> writes:

  >> There are various good ways to store the important change information,
  >     Yes, but storing that information in two different places, even when
  >     there isn't any overlap of info between the places, isn't one of them.

  > It is a fine method, which makes each kind of information convenient
  > for its purpose.

Seems to me that it would be a lot more convenient if the "what" and the
"why" of a change were in the same place.  That is where you are making
the split, ChangeLogs for the what and commit logs for the why?

The problem that your method alleviates, the doubling up of information,
simply doesn't exist when you are logging to a single place.

Your method does nothing to alleviate the problem of recurring conflicts
on the ChangeLog files.  Because of their very nature and purpose the
ChangeLog files get the most conflicts.  Normally very easy to resolve,
but still, a PITA.

Having the VC's built-in logging be the _only_ place your developers
write up their changes logs solves all of these issues.  And in my
experience, it does so painlessly.

We have never had a single problem, complaint or concern with using this
method of logging in SXEmacs, and I'd be only too happy to answer any
concerns that you or anyone else might have with moving to this
method.  Just Cc me or email me directly (I don't watch this list too

|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]