TBrowder wrote:
> I appreciate all the comments, and have no defense except I read the
> developer section of the book as well as HACKING and obviously didn't read
> them thoroughly enough. I will make the corrections suggested and
resubmit.
> (And Julian, thanks for your kind words.)
>
> However, before I resubmit the patch, I'll discuss my proposal in more
detail.
>
> Sometime last year (on the users list) I asked about three features we use
> heavily with CVS:
It is good idea to keep email threads to a single concept. It makes the
discussion far easier to follow.
Accordingly, I'm replying to your mail:
"Proposed New Feature (SVNROOT), '.svnignore', and 'rtag' (Revision
Aliases)"
in three seperate replies:
1. "Re: Proposed New Feature (SVNROOT)"
2. "Re: Proposed New Feature '.svnignore'"
3. "Re: Proposed New Feature 'rtag' (Revision Aliases)"
and I encourage people to continue discussion in each subthread seperately.
This is reply 3 of 3.
> rtag (and the command 'cvs history -T')
>
> Allows a quick glance at milestones of a project without cluttering
up
> the repository tree with changeable tags. Not changeable by the user.
> Output of 'cvs history -T' is guaranteed to be in reverse chronological
> order.
> In the future I shall propose implementation of the other two features I
> would like. Here are my initial thoughts on those:
> rtag
>
> The best idea I can come up with is to add the capability for an alias for
a
> revision (but, better than CVS, with a larger allowable character set) and
it
> would appear (if defined) in the log listing. A new alias may also be
added
> at a later date. I think it should not be changeable (except for
additions)
> by anyone except the administrator. The alias should be able to be used
in
> any svn command that uses a revision number or date. The log listing
command
> should have a switch to avoid showing entries without a revision alias.
That kind of gives subversion 2 types of tags - a recipe for confusion. I
think it would be better to tune the log reporting and clients to make use
of the existing method of tagging in subversion in ways that better suit
your needs.
For example, svn log could show copy sources, thereby effectively showing
that certain revisions are tagged.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 17 15:29:21 2004