On Tue, 20 May 2008, Adrian Schröter wrote:
On Tuesday 20 May 2008 16:10:18 wrote Pavol Rusnak:
Dominique Leuenberger wrote:
BUT with a small extension: the .changes files should be updated in
the same moment (or the api should use this info for the %changelog)
Generating commit message from changes file suits me better than the other way. What do others think?
Well, you may do multiple commits for just one changelog entry. The user of the package might not be interessted how many typos you put in during version upgrade ;)
What about that: if(changes file exits) { if(changes modified locally) { if(option --commitfromchanges) { set commit message to changes entry } else { do nothing } } else if(option --nochanges) { do nothing } else if(option --addchanges) { update last changes entry with commit message } else { add new changes entry } } else { do nothing :-) } That should fit all needs. Ciao -- http://www.dstoecker.eu/ (PGP key available)