Michael W Thelen wrote:
> * kfogel@collab.net <kfogel@collab.net> [2004-07-05 18:40]:
>
>>I guess this whole bit might change now, with the suggestion of
>>"-rHEAD:HEAD-10" syntax that others have made. (So I won't comment on
>>any of the parsing code.)
>>
>>As far as backwards compatibilty: When the server is new enough to
>>understand the new type of request, there should be no extra round
>>trip. When the server is old, it can error back to the client, which
>>the client can detect, and only *then* do an extra round-trip to
>>get the offset revision by number so it can re-request.
>>
>>So, here's a wicked question: shouldn't an offset of "HEAD-10" on a
>>file show you the last ten revisions *in which that file changed*, not
>>simply the revisions numbered HEAD through HEAD-10? :-) (Or did your
>>code already do that, and I just missed it?)
>
>
> If the repos HEAD revision is 100, I would expect HEAD:HEAD-10 to return
> the log messages for the range 100 through 90, regardless of how many
> changes were undergone by the target(s) in that range. I see "HEAD-10"
> as specifying a revision number independent of any targets.
I also think 'HEAD-10' should mean '90' here, independant of anything
else but the current head revision number.
> That's not to say that "give me the last 10 log messages" isn't a very
> common desire. I'm just not sure HEAD:HEAD-10 is the syntax for it.
> Something more like HEAD:HEAD-10C (last ten changes before HEAD), or a
> different command-line option entirely, like --limit 10, would make more
> sense to me.
--limit sounds very good.
or how about a comma to specify the maximum number of logs wanted?
e.g. HEAD:1,10 ( or just HEAD,10 )
======
c.a.t.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 6 10:01:26 2004