Linus Torvalds <[EMAIL PROTECTED]> writes:
> We're going through our docs and we have internal programs that we'll
> release for this so that you'll not just have docs but actually working
> code too. It just needs to be cleaned up a bit, and go through the proper
> channels (ever wonder why
Linus Torvalds [EMAIL PROTECTED] writes:
We're going through our docs and we have internal programs that we'll
release for this so that you'll not just have docs but actually working
code too. It just needs to be cleaned up a bit, and go through the proper
channels (ever wonder why open
neral Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILIT
eceived a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ *
+ * 1999/12/03: Linus Torvalds (cramfs tester and unarchive program)
+ * 2000/06/03: Daniel Quin
n the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Publi
General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ *
+ * 1999/12/03: Linus Torvalds (cramfs tester and unarchive program)
+ * 2000/06/03: Daniel Quinlan (CRC and length
David S. Miller writes:
> Ok, so lets be clear.
>
> Who is this facility really meant for? Linus (to decrease his
> workload), Ted (to assist him in keeping the todo/bug lists uptodate),
> or developers (who cares :-)?
>
> From the description, my take was that this thing is meant to help all
David S. Miller writes:
> [...] I don't want to sift through a log file on some web site
> etc. to find out what he's applied.
The log file is primarily for Ted (eventually a more automated
bug/TODO system).
> Very simply, (drumroll please) I want to run diff. :-)
I think this is an
Alexander Viro writes:
> Sigh... You know, some stuff is security-sensitive. Dunno about
> other folks, but in such situations I prefer to send the patches OOB
> to relevant maintainers. And they often go through several rewrites
> before they go into the tree. Having descriptions of _all_
Here is a proposal to improve the kernel development process. It was
co-written by Sebastian Kuzminsky, Linus Torvalds, Theodore Ts'o, and
myself. We are posting the proposal here for public review and
comment. Seb is the guy writing on the software; he's nearly done the
initial version.
Alexander Viro writes:
Sigh... You know, some stuff is security-sensitive. Dunno about
other folks, but in such situations I prefer to send the patches OOB
to relevant maintainers. And they often go through several rewrites
before they go into the tree. Having descriptions of _all_ pending
David S. Miller writes:
[...] I don't want to sift through a log file on some web site
etc. to find out what he's applied.
The log file is primarily for Ted (eventually a more automated
bug/TODO system).
Very simply, (drumroll please) I want to run diff. :-)
I think this is an orthogonal
David S. Miller writes:
Ok, so lets be clear.
Who is this facility really meant for? Linus (to decrease his
workload), Ted (to assist him in keeping the todo/bug lists uptodate),
or developers (who cares :-)?
From the description, my take was that this thing is meant to help all
three
13 matches
Mail list logo
