Re: svn commit: propchange - r13838 - svn:log

On Sat, Apr 02, 2005 at 03:20:50PM -0800, Justin Erenkrantz wrote:
> >controversy, it's probably just as well that the changes were
> >committed on the branch, but ordinarily trunk would (I think?) be a
> >better place for dist.sh maintenance (i.e., trunk for the master
> >change, then port it over to whatever release branches need it).
>
> The issue is that I thought dist.sh was associated with the branch that it
> was producing a release for - not the trunk which is a different release
> line. If that is incorrect, then I can merge whatever changes back into
> the trunk and also make it much more explicit to only use trunk/dist.sh in
> the docs. (Perhaps we should remove dist.sh from the branches?)

We need dist.sh on the branches due to minor differences (right now only
the URL to the book). I've always made an effort to make dist.sh that
is on trunk valid for any of the currently being released branches.

-- 
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org