[Paul Burba]
> We can certainly proceed with what you have so far (i.e. -cX-Y
> support) and if anybody wants to take up the -cX:Y banner, let them.
r1004727.
Peter
On Mon, Oct 4, 2010 at 12:43 PM, Peter Samuelson wrote:
>> On Sat, Oct 2, 2010 at 9:34 PM, Peter Samuelson wrote:
>> > Hmmm, in tests/cmdline/log_tests.py XFail(log_chanage_range), I see
>> > Lieven thought -c might someday take ranges with ":" instead of "-".
>> > But since the output uses "-",
[Paul Burba]
> FWIW diff/merge gained -c in 1.4 and log got it in 1.5.
Sounds right.
> > The following patch allows "-c" on the command line to use the same
> > range syntax as svn:mergeinfo. Thus you can cut and paste those ranges
> > from 'svn diff' output, into commands such as 'svn log' and
On Mon, 2010-10-04 at 11:28 -0400, Paul Burba wrote:
> On Sat, Oct 2, 2010 at 7:00 PM, Peter Samuelson wrote:
[...]
> > Hmmm, in tests/cmdline/log_tests.py XFail(log_chanage_range), I see
> > Lieven thought -c might someday take ranges with ":" instead of "-".
> > But since the output uses "-", I'
On Sat, Oct 2, 2010 at 7:00 PM, Peter Samuelson wrote:
>
> So, in 1.3 or 1.4 we gained '-c' as a convenience for specifying
> changesets as opposed to revision endpoints.
Hi Peter,
FWIW diff/merge gained -c in 1.4 and log got it in 1.5.
> Then in 1.5 we got the
> svn:mergeinfo property, which e
Strictly from the view of the non-developer and user of SVN;
I have only ever used the ":" for specifying a range.
But I do see the sanity in having the input match the output too.
If the ability to support both is indeed trivial - and if both cases are
"expected" by users - then that would certai
[Peter Samuelson]
> Is this, then, a worthwhile feature addition? I don't want to add
> syntax that nobody else wants. In particular, this patch highlights
> the existing inconsistency of ":" vs. "-" as range operators.
Hmmm, in tests/cmdline/log_tests.py XFail(log_chanage_range), I see
Lieven
7 matches
Mail list logo
