Re: The CHANGES file

On Wed, 2003-08-27 at 03:28, Tobias Ringstrom wrote:
> cmpilato@collab.net wrote:
> > Tobias Ringstrom <tobias@ringstrom.mine.nu> writes:
> >
> >>Why is the CHANGES file referring to a branch and not a tag?

This has been asked before, but I don't recall it ever being answered :)

> > Because at the time the CHANGES file is edited, there is no tag. And
> > after the tag is created, you can't edit the CHANGES file (duh, it's a
> > tag). :-)
>
> I could say that at the time the CHANGES file is edited, you do not
> know what the repository revision will be when you commit the change.

+1!
 
> I also think that referring to a tag is better than referring to a
> branch+revision for a number of other reasons:

+1!
>
> 1. It's a single thing, not two.
>
> 2. You can browse the code using a normal web browser. The branch
> is deleted from HEAD when the tag is created.
>
> 3. It's conceptually better. The tag is what's interesting, and
> the branch is only a "tool" to create the tag.

+1, +1, +1 :)

-- 
Seeya,
Paul
GPG Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE
	 If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org