This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH]: wwwdocs patches for svn move
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 26 Oct 2005 23:54:54 -0400
- Subject: Re: [PATCH]: wwwdocs patches for svn move
- References: <10510270337.AA27719@vlsi1.ultra.nyu.edu>
On Wed, 2005-10-26 at 23:37 -0400, Richard Kenner wrote:
> > Okay, if you consider it policy, then i will simply rewrite it, remove
> > the portion about creating branches and say "for further information
> > about how to create, and manage branches, as well as tips and hints,
> > see <wiki url>"
>
> I'm sorry, you must be confused, since Joseph and I are discussing
> cvswrite.html, and the branch information is in cvs.html.
>
> The quoted text above is from you!
But still irrelevant, since again, the *listing of branches is in
cvs.html*, cvswrite.html contained 3 lines on how to create a branch in
cvs, which i proposed removing to the wiki, which contains a much more
detailed explanation of how to create and manage branches.
>
> Excluding that, branch information changes, and somewhat frequently.
> That's exactly what a wiki is for.
>
> What the branches *are*, sure, but not the procedures used to create and
> maintain them.
Any developer can create a branch, that is the policy.
More than that is not, AFAIK. If you'd like to claim otherwise, please
provide some real detail
Procedures used to create and maintain individual branches that cvs.html
is listing, as well as their policies on patch acceptance, etc, have and
always will be up to the individual developers.
> But also, the list of branches is official
Uh, no it isn't. It's frequently out of date, in fact.
--Dan