On Mon, Sep 21, 2009 at 01:16:43PM -0500, Ryan Schmidt wrote:
> On Sep 21, 2009, at 12:40, William Yardley wrote:
> >On Fri, Sep 18, 2009 at 04:52:28AM -0500, Ryan Schmidt wrote:
> >>On Sep 17, 2009, at 17:45, William Yardley wrote:
> >>> We are getting some situations (not all the time) where a particular
> >>> entry seems to keep showing up in the svn log messages, even
> >>> when that
> >>> entry is no longer in the time range we're specifying. Is there
> >>> something wrong with the way I'm specifying the time?
> >> The first revision returned by "svn log -r A:B" will have a date
> >> before A. It could be one second before A, or it could be a year
> >> before -- whatever revision occurred immediately prior.
[...]
> >> For more information, read the box "Is Subversion a Day Early?" in
> >> this part of the book:
> >> http://svnbook.red-bean.com/en/1.5/svn.tour.revs.specifiers.html#svn.tour.revs.dates
> > But that specifically says:
> > If you specify a single date as a revision *without specifying a
> > time of
> > day* [emphasis mine].....
> I realize the scenario in the book isn't exactly the same as yours,
> but I've always found Subversion to behave the way I described --
> always including all revisions between A and B, and one revision
> before A -- but I haven't sampled a whole lot of repositories.
> > [in a different repo, which, if it matters, is a subdirectory of the
> > repo itself]
> You can have repositories within directories on the server, but
> there's no such thing as a repository being a subdirectory of a
> repository.
Ok, let me put it differently. We have one repository which contains a
number of subdirectories which we use as separate repositories. From the
perspective of SVN, it's all one repo, though.
From what I can tell, I am getting the behavior I expect (only entries
from within the exact time range specified) when I am running svn log on
any subdirectory of any top level repo. I am getting the behavior you
describe (all entries in the specified range +1 most recent) when
running svn log on any top level repo.
So it seems to me that svn is behaving not only differently from how the
documentation describes, but is also behaving inconsistently, depending
on whether svn log is being run against a top level repo or one of its
subdirectories.
FWIW, all repos are on the same server, which, in this case, is the same
machine that the client is running on. So the server, all repos, and the
client are all the exact same SVN version.
What I would like to know is whether I am likely to see the behavior I
expect if I upgrade to a newer version.
w
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2397553
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-21 20:43:26 CEST