Thanks for all the answers.
Yaakov.
On 2/8/06, Ryan Schmidt <subversion-2006Q1@ryandesign.com> wrote:
> On Feb 8, 2006, at 23:46, Yaakov Chaikin wrote:
>
> >>> I was looking at the logs of the top level in my BRANCH. I noticed
> >>> something like this:
> >>>
> >>> r34
> >>> r30
> >>> initial branch creation
> >>> ...
> >>> ...
> >>>
> >>> After doing svn log -r31, the log comes up empty.
> >>>
> >>> If I am at a branch and between revisions 30 and 34, someone updates
> >>> the trunk 4 times, should I be seeing this behavior?
> >>
> >> Oh. In that case, yes. That's expected. The revision number is global
> >> and applies to the repository as a whole.
> >
> > Ok, but what is weird to me is why wouldn't it show the log for the
> > specific revision number when I ask for it explicitly. Is that normal
> > and if so how does that make sense (what's the logic behind it)?
>
> "svn log" always operates on a path and a revision. If you supply no
> path, it uses the path of the working copy. If you supply no
> revision, it uses the revision of the working copy, or HEAD if you
> supplied a URL to a repository. You will only get log entries that
> apply to the path you gave. So if you're in a working copy of a
> branch, you'll only get log entries that apply to that branch, not
> the trunk or any other branch or tag. This is only natural: if I'm in
> a working copy of project foo and I ask for a log of all changes to a
> file, I surely don't want to be bothered with the log entries of any
> other project or path or file.
>
> If you want to see the log of revision 31, regardless of whether that
> change occurred beneath the path of the current working copy or not,
> then provide the URL to the repository:
>
> svn log -r31 url://to/repository
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 9 00:21:46 2006