svn commit: r336046 - in head/sys: amd64/include i386/include sys

[Rodney W. Grimes]

[ Charset ISO-8859-1 unsupported, converting... ]
> On Mon, 2018-07-09 at 14:58 +0000, Alexey Dokuchaev wrote:
> > On Mon, Jul 09, 2018 at 09:23:27AM +0000, Brooks Davis wrote:
> > > 
> > > On Sat, Jul 07, 2018 at 02:18:56AM +0000, Alexey Dokuchaev wrote:
> > > > 
> > > > On Fri, Jul 06, 2018 at 10:52:37PM +0300, Konstantin Belousov wrote:
> > > > > 
> > > > > On Fri, Jul 06, 2018 at 07:50:25PM +0000, Konstantin Belousov wrote:
> > > > > > 
> > > > > > New Revision: 336046
> > > > > > URL: https://svnweb.freebsd.org/changeset/base/336046
> > > > > > 
> > > > > > Log:
> > > > > > ? Revert to recommit with the proper message.
> > > > > I am sorry for the second mistake of the same sort in the day.
> > > > It would be much easier if we'd allowed "svn propedit --revprop svn:log".
> > > Not going to happen.??That would completely trash the ability to use git
> > > exports.
> > Yeah, I've heard of it.??It's a pity that SVN users have to suffer for the
> > benefit of some obscure, unofficial VCS. :-(
> > 
> > ./danfe
> > 
> 
> I think if git weren't in the way, what you would hear instead would be
> arguments against doing so from those who believe that a version
> control system exists to maintain an *immutable* history of changes to
> the source base. My voice might be one of those, unless there were some
> very tight controls on who could use such a feature and under what
> conditions.

Or svn could grow the proper features to have immutability, you just
have to revision control the log entry, something that is at least
40 year old technology in the paper world of document control.

I have never understood why this feature is missing from every
automated VCS system I have seen.

-- 
Rod Grimes                                                 rgrimes at freebsd.org