On Wednesday 17 August 2005 08:16 am, Henrik Brix Andersen wrote:
> On Tue, 2005-08-16 at 18:18 -0400, Mike Frysinger wrote:
> > logic:
> >  - i'm lazy
> That's not a valid argument - you can use a bash function for calling
> echangelog and repoman as shown numerous times on this list.

it was part joke and part seriousness ... i already have my commits scripted 
with echangelog/repoman, but that isnt the point

> >  - i hate typing the samething twice (yes, bash scripting with echangelog
> > can kind of take care of this) ... it doesnt handle if you want to use
> > different commit messages for different files
> Can you give an example of why you would want to use different commit
> messages in a single commit?

i delete one version for being old, stabilize another ebuild, and add yet 
another ebuild as a rev bump

> >  - forces cvs log messages to actually be worthwhile to read and makes
> > browsing cvs history much nicer (it's very easy to look at the
> > differences between two files and match up a good commit message rather
> > than trying to figure out what message in the ChangeLog goes with it,
> > assuming there is one)
> See my first answer (bash function).

which does not matter if  you commit individual files firest with different 
messages before running your bash funcs

it also pollutes the cvs log history for files ... if i make different fixes 
to different files but only commit with one message, you easily get a lot of 

> >  - easily standardize ChangeLog format wrt to header, copyrights,
> > licensing, message formatting, name/date format
> Already done by echangelog.

not everyone uses echangelog

> >  - generate dates in UTC down to the second rather than having devs hand
> > type them in their local timezone for just the current day
> I thought echangelog already did this based on TZ?

it does, but not everyone uses echangelog

> >  - maybe some other things i havent thought of
> >  - i'm lazy
> See my first answer (bash function).

heaven forbid you get a joke and laugh once in a while
gentoo-dev@gentoo.org mailing list

Reply via email to