I think your other email was right on the money, although I haven't
tested it for myself yet.
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?
Thanks,
Yaakov.
On 2/8/06, Ryan Schmidt <subversion-2006Q1@ryandesign.com> wrote:
> On Feb 8, 2006, at 19:04, Yaakov Chaikin wrote:
>
> > I noticed looking at the logs that the revision numbers get skipped
> > once in a while. After trying things out, I realized that these must
> > be file/dir property changes. However, even if I use the command-line
> > and commit property changes (even with comments), they are not showing
> > up in the log. In fact, even if I do svn log -rSomeNumber that doesn't
> > show up in the log, it still doesn't show me that log.
> >
> > How do I get at the log for the property changes?
>
> I don't think that's what's happening, and I don't think it has to do
> with whether a change is a property change or something else.
>
> If you're running "svn log" in your working copy, have you first
> updated the working copy with "svn up"? If not, you'll only see logs
> up to the revision the repository is currently at.
>
> If I'm misunderstanding and you're doing something different, it
> would help if you could provide a transcript of the commands you
> enter and their output, and how this output differs from your
> expectations.
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 8 23:30:20 2006