From: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] Re: Kernel Development and Cogito
Date: Wed, 10 Aug 2005 20:24:17 +0000 [thread overview]
Message-ID: <20050810202417.GA5387@arthur.home> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1019 bytes --]
On Wed, Aug 10, 2005 at 01:23:14PM -0400, Gabriel Devenyi wrote:
> I would like to start working on some kernel-janitor stuff, and I've
> cloned Linus' tree using Cogito (cg-clone). My issue is that I can't
> find any documentation on how I would go about working on this tree now,
> like if I make a change, how do I create a patch that I can send off to
> kernel-janitors, and LKML, similarly, how would I reset my tree to be
> exactly like Linus' if I muck something up badly. Is there a document
> out there describing the usage of Cogito, or can someone outline the
> basics of using Cogito to dump my changes for distribution? Thanks for
> your help!
This one is from Cogito itself:
http://www.kernel.org/pub/software/scm/cogito/README
Jeff Garzik wrote a Git "howto" (the system that lives under Cogito):
http://linux.yyz.us/git-howto.html
IIRC Randy Dunlap also wrote something, but I can't find it.
Erik
--
Erik Mouw
J.A.K.Mouw@its.tudelft.nl mouw@nl.linux.org
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next reply other threads:[~2005-08-10 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 20:24 Erik Mouw [this message]
2005-08-10 20:34 ` [KJ] Re: Kernel Development and Cogito Randy.Dunlap
2005-08-10 20:58 ` Gabriel Devenyi
2005-08-10 23:31 ` Ryan Anderson
2005-08-11 15:08 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050810202417.GA5387@arthur.home \
--to=j.a.k.mouw@its.tudelft.nl \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.