subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dane Kantner <>
Subject Re: How to check out a project based on commit time rather than rev?
Date Fri, 18 May 2018 20:36:02 GMT
 svn log -v -r {2012-05-06}:{2017-01-01} <URL to server side directory>  is
not reliable though as it doesn't actually consistently return the data
correctly ;  there has been a past topic on this and it's been explained as
a known defect due to how it was implemented.  You're better off trying to
determine the revision number in play at the time of the start, and at the
time of the end, then using the revision numbers instead.

On Fri, May 18, 2018 at 2:14 PM, Nathan Hartman <>

> On Fri, May 18, 2018 at 12:35 PM Bo Berglund <>
> wrote:
>> On Fri, 18 May 2018 18:00:21 +0200, Bo Berglund
>> <> wrote:
>> >Obviously this is a "for dummies" question but I *have* looked at the
>> >svnbook but I cannot still find how to do this:
>> I did not read good enough!
>> This worked fine to get the information I needed concerning active
>> revision numbers:
>> svn log -v -r {2012-05-06}:{2017-01-01} <URL to server side directory>
>> > log.txt
>> So now I can use this to compare the files and add what is lacking to
>> the wc I have checked out to make it be current at the date I need.
>> Sorry for the noise!
>> --
>> Bo Berglund
>> Developer in Sweden
> I've wondered why there isn't a checkout or update command that takes a
> date and time but usually I look in the log to figure out what is the
> revision number.
> I don't know how CVS works but with Subversion, when you checkout an old
> revision, you get the directories and files exactly as they looked in that
> revision (including files that were not changed in that revision). Think of
> it as a snapshot of how everything looked at that moment. Just make sure
> each time you commit that Subversion knows about all the files you intend
> to keep -- ie that svn st in the working copy directory does not show '?'
> on files that should be under version control. You're allowed to have
> unversioned files alongside versioned ones, eg for intermediate build
> artifacts, editor bak files, and other junk.

View raw message