Dan Nicholson wrote:
> Sorry to keep pestering, but you normally want both to be there. Stuff
> in tags is supposed to be static. The idea being that you can use
> 6.3-rc1 as a benchmark to compare the next rc or release. During this
> phase, we would have
>
> trunk
> branches/6.3
> tags/6.3-rc1
>
> trunk moves forward, diverging from branches/6.3 as new things are
> merged in. Things get fixed in branches/6.3 (and possibly in trunk if
> it still applies). Eventually, we have rc2. Now we have
>
> trunk
> branches/6.3
> tags/6.3-rc{1,2}
>
> That's convenient since now you have a copy of the tree from rc1 and
> rc2. With SVN, this is not enforced, and it's also bloated as a full
> copy is done, but it's still a good idea in the meantime. That's why
> the branches/tags functionality is there.
>
> When 6.3 final is released, we can probably remove the -rc* tags and
> maybe the 6.3 branch if we don't expect to backport any more fixes.
>
> Do you agree?
Yes, I can do that (just did). I tend to disagree with your comment
about being bloated, at least in the server. Copies are made with
pointers, not by doing a complete copy. On the clients, an update,
export, or checkout does make copies.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
