Re: Fwd: Forcing commit of unmodified file
* Erik Huelsmann (email@example.com) [070613 07:59]:
> On 6/13/07, Arnauld Van Muysewinkel <firstname.lastname@example.org> wrote:
> >2007/6/13, Andreas Mahel <email@example.com>:
> >> Arnauld Van Muysewinkel wrote:
> >> >
> >> >
> >> > On another hand, I still don't understand why SVN is preventing this...
> >> An alternate use case for your problem might be called "Extend an
> >> existing log message". This might be considered less harmful (by
> >> admins);
> >Indeed, that's my use case. It's OK as long as no log message can be
> >*changed*, which is important for compliance reasons.
> Why's that? Your repo admin can save the old message before replacing
> it with the new one. That'll provide him/you with the audit trail
Your revprop change hook could even enforce the change, by only allowing
the commit if the new log message is an extension of the old one.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Q: What is the most annoying thing on usenet and in e-mail?
Received on Wed Jun 13 21:29:37 2007
This is an archived mail posted to the Subversion Users