You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jojakim Stahl <jo...@jojakim.de> on 2007/07/12 13:21:01 UTC

Feature Request: copy-to information in svn log

I propose to add copy-to information to the output of svn log. This is to see, 
which revision has been "tagged" and with which name. If you take a copy, you 
can see the origin of the copy (copy-from). It would be necessary to add the 
destination to each origin (copy-to).

Use case:
repo structure:
  project/trunk
  project/tags
  project/branches

Every time I prepare a release, I "tag" the current trunk by copying to 
project/tags, giving the version as the name.
Example: svn cp project/trunk project/tags/v5.1.0.3 -m "TAG: Version 5.1.0.3"

If I call svn log project/trunk it is important to me to see which revision 
has been "tagged" and the "tag"'s name. Currently, there is no simple way to 
do this.


Question:
Should svn log only list the copy-to pathes of the path on which svn log has 
been called? Or should svn log show also the copy-to pathes of all parent or 
child pathes?

Example:
project/trunk/a/b
project/tags/cp-t       copied from project/trunk
project/tags/cp-a       copied from project/trunk/a
project/tags/cp-b       copied from project/trunk/b

What shall svn log project/trunk/a show?
A) copy-to: project/tags/cp-t       (because a is included in cp-t as a child?)
B) copy-to: project/tags/cp-a       (FOR SURE!)
C) copy-to: project/tags/cp-b       (because something out of a is in cp-b?)

On which revision shall the infos be shown? On the last changed revision of a 
before the copies have been taken? That is what makes sence only. Because 
showing log of the revision in which the copy has been committed is not a good 
option. Imagine you make a copy 100 revision later than what revision you 
specify in your copy.

I'm sorry for the somewhat long post, but this is a feature which I'm missing 
but where I am not 100% sure how to solve in context of SVN. The origins of 
this feature request is perhaps CVS, where I could see the labels of an 
revision of a file. Something like this I though of in concepts of SVN.

Please comment on this...

Jojakim Stahl

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

Re: Feature Request: copy-to information in svn log

Posted by Erik Huelsmann <eh...@gmail.com>.
On 7/12/07, Jojakim Stahl <jo...@jojakim.de> wrote:
> I propose to add copy-to information to the output of svn log. This is to see,
> which revision has been "tagged" and with which name. If you take a copy, you
> can see the origin of the copy (copy-from). It would be necessary to add the
> destination to each origin (copy-to).
>
> Use case:
> repo structure:
>   project/trunk
>   project/tags
>   project/branches
>
> Every time I prepare a release, I "tag" the current trunk by copying to
> project/tags, giving the version as the name.
> Example: svn cp project/trunk project/tags/v5.1.0.3 -m "TAG: Version 5.1.0.3"
>
> If I call svn log project/trunk it is important to me to see which revision
> has been "tagged" and the "tag"'s name. Currently, there is no simple way to
> do this.
>
>
> Question:
> Should svn log only list the copy-to pathes of the path on which svn log has
> been called? Or should svn log show also the copy-to pathes of all parent or
> child pathes?
>
> Example:
> project/trunk/a/b
> project/tags/cp-t       copied from project/trunk
> project/tags/cp-a       copied from project/trunk/a
> project/tags/cp-b       copied from project/trunk/b
>
> What shall svn log project/trunk/a show?
> A) copy-to: project/tags/cp-t       (because a is included in cp-t as a child?)
> B) copy-to: project/tags/cp-a       (FOR SURE!)
> C) copy-to: project/tags/cp-b       (because something out of a is in cp-b?)
>
> On which revision shall the infos be shown? On the last changed revision of a
> before the copies have been taken? That is what makes sence only. Because
> showing log of the revision in which the copy has been committed is not a good
> option. Imagine you make a copy 100 revision later than what revision you
> specify in your copy.
>
> I'm sorry for the somewhat long post, but this is a feature which I'm missing
> but where I am not 100% sure how to solve in context of SVN. The origins of
> this feature request is perhaps CVS, where I could see the labels of an
> revision of a file. Something like this I though of in concepts of SVN.
>
> Please comment on this...

It's a long-time wish to add copy-to information to svn log and other
commands. It would enable forward-searching in the directory tree and
with that many usefull applications. For now, it's not possible to
show the information since it's not stored in the repository (which
only stores copy-from). Therefore on larger repositories, it would be
very computational intensive to deduce the required information.

It'll probably be added some day, but for now there were more
important features to add.

Patches and design documents welcome on dev@!

HTH,


Erik.

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