mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@gmail.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [RFC] HOWTO do Linux kernel development - take 3
Date: Thu, 17 Nov 2005 06:59:23 -0600	[thread overview]
Message-ID: <625fc13d0511170459u73b9501gee6a154073059aa@mail.gmail.com> (raw)
In-Reply-To: <81b0412b0511170447j36efc887idf3a942443197c56@mail.gmail.com>

On 11/17/05, Alex Riesen <raa.lkml@gmail.com> wrote:
> On 11/17/05, Greg KH <gregkh@suse.de> wrote:
> > 2.6.x kernel tree
> > -----------------
> > 2.6.x kernels are maintained by Linus Torvalds, and can be found on
> > kernel.org in the pub/linux/kernel/v2.6/ directory.  Its development
> > process is as follows:
> >   - As soon as a new kernel is released a two weeks window is open,
> >     during this period of time maintainers can submit big diffs to
> >     Linus, usually the patches that have already been included in the
> >     -mm kernel for a few weeks.  The preferred way to submit big changes
> >     is using git (the kernel's source management tool, more information
> >     can be found at http://git.or.cz/) but plain patches are also just
> >     fine.
>
> The http://git.or.cz/ is broken. Maybe
> http://www.kernel.org/pub/software/scm/git/docs/ (manual) or
> http://gitscm.org/ ?

Broken how?  It works for me...

josh

  reply	other threads:[~2005-11-17 12:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17  7:09 Greg KH
2005-11-17 12:47 ` Alex Riesen
2005-11-17 12:59   ` Josh Boyer [this message]
2005-11-17 13:07     ` Alex Riesen
2005-11-24  6:16 James G. Sack (jim)
2005-11-28  4:33 ` Randy.Dunlap

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=625fc13d0511170459u73b9501gee6a154073059aa@mail.gmail.com \
    --to=jwboyer@gmail.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®