[I assume you didn't intend to remove the dev@ list from the cc: list,
so I've re-added it.]
On Fri, Aug 26, 2005 at 03:29:53PM +0400, Artem Shvorin wrote:
> > > I'd like to be able to commit just a log without changes. CVS has such
> > > feature:
> > > cvs ci -f files...
> > >
> > > Are there any reason not to implement similar option for subversion?
> >
> > If I understand correctly, the Subversion backend can already handle a
> > revision with no changes (though I don't know if it can handle file-changes
> > with empty deltas, which I think you'd need to associate the revision
> > with the files), though I don't think you are supposed to be able to produce
> > such a revision with the current libraries/client...
> >
> > But what's the use case for such a feature anyway? The only time I've ever
> > seen it used is to be able to add a note to say something like 'last checkin
> > was for bug xxx', and that can be more easily done in Subversion by editing
> > the svn:log revision property.
>
> The default repository settings discourage from modifying the revision
> properties (we have to toggle the hook script or use svnadmin). This
> seems to be ok, since history is being lost. I agree that subj feature
> is not very useful, but I hope it's easy enough to implement.
It is only the _default_ settings that prevent you from modifying svn:log,
and 'mv pre-revprop-change.tmpl pre-revprop-change' is enough to enable it.
So what was the use case for this feature? Is it just that you want to be
able to add to log messages? Because if so, I really think you're better
off just enabling the hook script (or something slightly more complex, if
you only want users to be able to append to svn:log).
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 26 13:53:23 2005