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

Re: svn commit: r10276 - in branches/1.1.x: . subversion/include subversion/libsvn_client subversion/libsvn_ra_svn subversion/mod_dav_svn subversion/svnserve

From: Max Bowsher <maxb_at_ukf.net>
Date: 2004-07-14 21:57:21 CEST

kfogel@collab.net wrote:
>>> Log:
>>> Merge r10262:10263 from trunk.
>>> Approved by: lundblad, breser, sussman
>>>
>>> * STATUS: Remove merged entry.
>>>
>>> ----------------------------------------------------------------------

--
>>>   r10262 | lundblad | 2004-07-13 19:57:05 +0100 (Tue, 13 Jul 2004) | 4
lines
>>>
>>>   Comment and docstring fixes for r10047, 10188 and 10189.
>>>
>>>   Thanks to kfogel for pointing these out.
>>>
>>>   ----------------------------------------------------------------------
--
>>>   r10263 | lundblad | 2004-07-13 20:13:14 +0100 (Tue, 13 Jul 2004) | 2
lines
>>>
>>>   Fix compile error introduced in 10262.  Shouldn't do many things as
>>> once...
>
> Also, please always prefix to revision numbers with "r".  That is, the
> regular expression
>
>    r[0-9]+
>
> should find all revision numbers.  And when you're merging one
> revision, just say the revision you merged, not that command you had
> to issue to merge it.  For example, just say
>
>    "Merge r10263 from trunk."
>
> not
>
>    "Merge r10262:10263 from trunk."
>
> (But if you *are* going to express a range, then still keep both "r"s,
> as in "r10262-r10263.  It's just in this case, there's no need to give
> a range, since it's really a merge of one revision, r10263.)
Um, no, it's 2 revisions - note the 2 log messages above!
But I can see how this could be ambiguous. Will propedit.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 14 21:58:46 2004

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.