lkml.org 
[lkml]   [2002]   [Apr]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Remove Bitkeeper documentation from Linux tree
If they start to be tools that are used to submit changes to the kernel
then yes they should be included.

remember that the reason for the bitkeeper documentation is to help people
setup a tree that linux (and others) can pull from, not to help people
setup their own tree just for them to hack on. Currently none of the tree
maintainers use cvs/rcs/sccs/arch/subversion/aegis/prcs in such a way that
there is anything that someone hacking the kernel needs to do to be
compatable (other then following the existing documentation for sending
patches) but for bitkeeper there is so this documentation is needed.

David Lang


On Sat, 20 Apr 2002, Roman Zippel wrote:

> Hi,
>
> Jeff Garzik wrote:
>
> > Guess what else? You are taking away freedoms by restricting speech,
> > making documents less available than they previously were.
>
> So we soon include cvs/rcs/sccs/arch/subversion/aegis/prcs usage
> information as well?
> You certainly don't want to restrict the freedoms of other users?
>
> bye, Roman
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:25    [W:0.841 / U:0.152 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site