Aw: Re: [PATCH 11/13] Remove obscure reference from "Examples"
> > > > - A "test" tree into which patches are initially placed so that they > > can get some exposure when integrated with other ongoing development. > > - This tree is available to Andrew for pulling into -mm whenever he > > - wants. > > This drops useful information (namely, that Tony was publishing > history for two people to consume). Perhaps it should spell out "the > bleeding-edge -mm tree"? > This is even worse for me;-) For everyone not involved in Linux kernel development this sentence completely makes no sense. Is there perhaps a more general description for the situation? --- Thomas -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 11/13] Remove obscure reference from "Examples"
Thomas Ackermann wrote: > --- a/Documentation/user-manual.txt > +++ b/Documentation/user-manual.txt > @@ -2131,8 +2131,6 @@ He uses two public branches: > > - A "test" tree into which patches are initially placed so that they > can get some exposure when integrated with other ongoing development. > - This tree is available to Andrew for pulling into -mm whenever he > - wants. This drops useful information (namely, that Tony was publishing history for two people to consume). Perhaps it should spell out "the bleeding-edge -mm tree"? Jonathan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 11/13] Remove obscure reference from "Examples"
Thomas Ackermann writes: > Signed-off-by: Thomas Ackermann > --- > Documentation/user-manual.txt | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt > index aa6bfab..0d3f04e 100644 > --- a/Documentation/user-manual.txt > +++ b/Documentation/user-manual.txt > @@ -2131,8 +2131,6 @@ He uses two public branches: > > - A "test" tree into which patches are initially placed so that they > can get some exposure when integrated with other ongoing development. > - This tree is available to Andrew for pulling into -mm whenever he > - wants. > > - A "release" tree into which tested patches are moved for final sanity > checking, and as a vehicle to send them upstream to Linus (by sending Hmm What part is obscure and why does this need to be removed? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
