dlr@tigris.org wrote:
> Author: dlr
> Date: Wed Oct 11 17:11:57 2006
> New Revision: 21898
>
> Log:
> * STATUS: Nominate r21897, and approve r20992.
>
> Modified:
> branches/1.4.x/STATUS
>
> Modified: branches/1.4.x/STATUS
> URL: http://svn.collab.net/viewvc/svn/branches/1.4.x/STATUS?pathrev=21898&r1=21897&r2=21898
> ==============================================================================
> --- branches/1.4.x/STATUS (original)
> +++ branches/1.4.x/STATUS Wed Oct 11 17:11:57 2006
> @@ -155,6 +155,16 @@
> Votes:
> +1: lgo
>
> + * r21897
> + Add validation of the HEAD argument passed to 'svnmerge.py init'.
> + Justification:
> + This common gotcha otherwise results in an ugly stack trace with
> + no meaningful feedback to the user.
> + Votes:
> + +1: dlr
I'm thinking instead of just merging this change over, why don't we nominate all
the unmerged changes to the svnmerge*py files? There's a number of changes
there and I'd like to see 1.4.1 have all the fixes. Besides, I tried to merge
r21897 into 1.4.x and it didn't merge cleanly.
I don't know if our "no new features" policy for 1.4.x releases applies to
scripts, or even those in contrib/. which are not "officially" supported by us.
The only revision to svnmerge.py that affected other files was r19953, which we
could leave out.
Regards,
Blair
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 12 02:53:22 2006