[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r36214 - in branches/1.6.x: . subversion/svn

From: Stefan Sperling <stsp_at_elego.de>
Date: Sun, 1 Mar 2009 15:25:04 +0000

On Sun, Mar 01, 2009 at 01:49:48AM +0100, Greg Stein wrote:
> That applies to partial committers fixing "obvious" things outside
> their normal allowed area. It does not apply to merging changes onto a
> release branch. The description of change management for release
> branches even refers to obvious fixes when talking about *voting* for
> those types of changes.

Where?

All I could find is that "Obvious fixes do not require '(rX only)'
to be mentioned".

I don't see a problem with invoking the obvious fix rule in this case.
Arfrever mentioned that he invoked the rule, making clear to everyone
what his reasoning for merging the change is. So the only thing worth
arguing is whether we all agree the commit was an obvious fix or not.

> And (IMO) merging changes into a release should be deferred to the RM
> simply for politeness' sake.

I have made merges into release branches before.
I'd say once there are enough votes, it does not matter who does the
merging. I see no issue of politeness.

Stefan
Received on 2009-03-01 16:25:32 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.