On 2/7/14, 10:45 PM, Ben Reser wrote:
> Finally, save yourself some trouble and learn the ^/ syntax:
> https://subversion.apache.org/docs/release-notes/1.5.html#externals-relative-urls
And it's clearly too late since I linked to the wrong relative URL release
note. I meant:
https://subversion.apa
On 2/7/14, 4:28 PM, Kyle Sluder wrote:
> % svn mergeinfo --show-revs=eligible -r202859 ${Repository Root}/trunk
> r200832
> r200833
> r200836
> r200837
> [ ... snip ...]
>
> Notice that -r200832 is much earlier than the r202859 argument which was
> passed on the command line.
>
> My wild guess is
On Fri, Feb 7, 2014, at 04:18 PM, Kyle Sluder wrote:
> And if I replace the "…branches/4.0.2" with "…trunk", I can see all the
> revisions that haven't been merged from trunk yet.
Hmm, I spoke too soon:
% svn mergeinfo --show-revs=eligible -r202859 ${Repository Root}/trunk
r200832
r200833
r200836
On Fri, Feb 7, 2014, at 03:37 PM, Bob Archer wrote:
> The help says:
>
> (some commands also take ARG1:ARG2 range)
>
> Did you not get what you wanted without specifying a range?
Hmm, that looks promising:
% svn mergeinfo --show-revs=eligible -r202859 ${Repository
Root}/branches/4.0.2
r202880
r
> I created a branch (4.0.x) from trunk. Work progressed on trunk and was
> selectively merged down to the 4.0.x branch.
>
> The intent was to do our next release off this branch and then kill it.
> Subsequent releases would come from the trunk (or branches thereof).
>
> Unfortunately plans chang
I created a branch (4.0.x) from trunk. Work progressed on trunk and was
selectively merged down to the 4.0.x branch.
The intent was to do our next release off this branch and then kill it.
Subsequent releases would come from the trunk (or branches thereof).
Unfortunately plans changed, and we nee
