On Feb 2, 2010, at 09:07, Tim Landscheidt wrote:
> Ryan Schmidt wrote:
>
>> $ svn log -r '{2010-01-01}' --limit 1 -q \
>> http://svn.macosforge.org/repository/macports
>>
>> r62218 | portin...@macports.org | 2009-12-31 18:5
Ryan Schmidt wrote:
>> Anyhow, is there a "proper" way to deduce a revision num-
>> ber from a date for a given path? At the moment (I'm brows-
>> ing the output of cvs2svn to see if the repository has been
>> converted correctly), I use "svn log --verbose" on the
>> trunk.
> Yes, you can use "s
On Jan 26, 2010, at 11:19, Tim Landscheidt wrote:
> Anyhow, is there a "proper" way to deduce a revision num-
> ber from a date for a given path? At the moment (I'm brows-
> ing the output of cvs2svn to see if the repository has been
> converted correctly), I use "svn log --verbose" on the
> trunk
Felix Gilcher wrote:
> you seem to be confused about Peg revisions, you could read about them here:
> http://svnbook.red-bean.com/en/1.5/svn.advanced.pegrevs.html
> In short, a peg revions (@2, @HEAD, ...) denotes that the item you're looking
> for can be found at the specified path at the spe
On Jan 26, 2010, at 03:48, Felix Gilcher wrote:
> On Jan 26, 2010, at 2:26 AM, Tim Landscheidt wrote:
>
>> [snip] Is there a way to express the '-r {DATE}' syntax
>> with the "@" suffix? "@{2009-01-01}" seems to be ignored:
>
> [snip] A peg revision must be a revision number and cannot be a date
Hi Tim,
you seem to be confused about Peg revisions, you could read about them here:
http://svnbook.red-bean.com/en/1.5/svn.advanced.pegrevs.html
In short, a peg revions (@2, @HEAD, ...) denotes that the item you're looking
for can be found at the specified path at the specified revision. So
Hi,
I'm a bit baffled by the following behaviour on a small test
repository where in r2 the directory a and file a/b exist
and are deleted in HEAD/r4:
| [...@passepartout ~]$ svn --version
| svn, version 1.6.6 (r40053)
|compiled Nov 8 2009, 13:09:20
| [...]
| [...@passepartout ~]$ svn list f
