Logs of property changes

[Yaakov Chaikin <ya...@gmail.com>]

Hi,

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?

Thanks,
Yaakov.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Logs of property changes

[Yaakov Chaikin <ya...@gmail.com>]

Thanks for all the answers.

Yaakov.

On 2/8/06, Ryan Schmidt <su...@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

Re: Logs of property changes

[Ryan Schmidt <su...@ryandesign.com>]

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

Re: Logs of property changes

[Yaakov Chaikin <ya...@gmail.com>]

On 2/8/06, Ryan Schmidt <su...@ryandesign.com> wrote:
> On Feb 8, 2006, at 23:28, 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)?

Yaakov.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Logs of property changes

[Ryan Schmidt <su...@ryandesign.com>]

On Feb 8, 2006, at 23:28, 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.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Logs of property changes

[Yaakov Chaikin <ya...@gmail.com>]

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 <su...@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

Re: Logs of property changes

[Ryan Schmidt <su...@ryandesign.com>]

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

Re: Logs of property changes

[Ryan Schmidt <su...@ryandesign.com>]

On Feb 8, 2006, at 23:13, Yaakov Chaikin wrote:

> On 2/8/06, Royce Fessenden <rf...@dmp.com> wrote:
>> Property changes are not logged!
>
> Yet, updating a property does increment the revision number.
>
>> (That's why the ability to edit log
>> messages is disabled by default.)
>
> Well, I did succeed in logging change of a property and it did show up
> in the logs. You are saying that property changes do no require a log
> message by default, but I can provide one if I want? Just wanted to
> make sure I understand what you are stating.

There are two different kinds of properties.

There are the properties that apply to files and directories, like  
svn:keywords, svn:eol-style, svn:executable and so forth. You change  
these in a working copy, and then commit the change, which creates a  
new revision just like any other change in a working copy.

The other kind of properties are revision properties, which are  
things like the date of a commit, its author, the log message, and so  
forth. These are also called unversioned properties, because they  
apply directly to a revision, meaning if you were to change them,  
this wouldn't cause a new revision to be created; rather, the  
property of the existing revision would be overwritten, and the  
previous values would be lost forever. (They are not versioned like  
the rest of the things in your repository are.) For this reason, the  
ability to change revision properties is turned off by default, and  
if you want to enable this ability for some reason (like letting  
people fix typos in commit messages after the fact) you need to  
install a pre-revprop-change hook to allow it. You're also advised in  
this case to log the change somewhere, for example by sending an  
email to your development group.

Yaakov was talking about ththe first type of property in his original  
posting; Royce is talking about the second.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Logs of property changes

[Yaakov Chaikin <ya...@gmail.com>]

On 2/8/06, Royce Fessenden <rf...@dmp.com> wrote:
> Property changes are not logged!

Yet, updating a property does increment the revision number.

> (That's why the ability to edit log
> messages is disabled by default.)

Well, I did succeed in logging change of a property and it did show up
in the logs. You are saying that property changes do no require a log
message by default, but I can provide one if I want? Just wanted to
make sure I understand what you are stating.

> The revisions numbers are shared across an entire repository. i.e. All
> folders, branches, tags, etc.  The missing numbers are most likely from
> changes to something that is not related to the folder you are looking at.

I see. Now it makes more sense... I'll have to check this out.

Yaakov.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org