[RFC] Policy change for ChangeLog

[Derek Atkins]

Neil Williams <linux at codehelp.co.uk> writes:

> What I'd like is that the ChangeLog entries become "recommended" but not 
> "mandatory".
>
> Just getting rid of the warning about reverting any changes that lack a 
> ChangeLog entry would be a welcome step.

You're taking the 'warning' way too literally.  The idea is to keep a
log (NOT in the SCM metadata) of changes made to GnuCash.  When was
the last time a change was reverted because it lacked a ChangeLog
entry?

Now, don't let this mean you're welcome to stop making ChangeLog
entries.  See my previous email about that.  I think it's perfectly
reasonable in certain cases (in particular cases where you're not
changing real code) to /not/ enumerate the changed files in the
ChangeLog.  BUT...  I think you still MUST make a log entry!

>> Personally I feel you should always run an "svn diff | more" prior
>> to the commit to make sure you're only committing the change(s) you
>> want.
>
> (Can't think why, but my diff's tend to be so large I need to redirect it to a 
> file!)
> :-)

Okay, if you're going to be pedantic, personally I feel you should
always run "svn diff" and audit the output using whatever method you
prefer, but you should ALWAYS audit the "svn diff" before you commit.
Better?   :-P

>> Then C-x C-s the ChangeLog buffer, 
>> M-w to copy the changelog entry, and then C-y once you get the svn commit
>
> And in English for those who don't speak emacs ?!?!!

"The [Save] the ChangeLog buffer, [copy-to-cut-buffer] to copy the
changelog entry, and then [yank-from-cut-buffer] once you get the
svn commit"

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available