mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Latest staging stuff
Date: Thu, 11 Dec 2008 11:53:25 -0800	[thread overview]
Message-ID: <20081211195325.GA7978@kroah.com> (raw)
In-Reply-To: <43e72e890812111146n1b9b0d07y99cd8cea3d72e952@mail.gmail.com>

On Thu, Dec 11, 2008 at 11:46:41AM -0800, Luis R. Rodriguez wrote:
> Greg,
> 
> Where do I get stuff to send patches against your latest staging? I
> thought it would be your staging git tree:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> 
> But this doesn't seem to have the latest. I actually see more later stuff on:
> 
> http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/staging/

Yes, that is correct.

> What is the difference between what you maintain in these?

The old staging.git tree is obsolete, I need to go delete the thing,
sorry about that.

> I take it there is no actual git tree that is not just a directory
> with patches for staging huh? It seems I would have to apply all the
> patches in gregkh/gregkh-2.6/patches/staging/ and then send stuff
> against it.

Yes, that is exactly the thing to do.

Or, you can grab the linux-next tree and send me patches against that,
as it includes my staging patch set inside of it and it is resynced
every night.

So, if you like git, you might want to stick with linux-next and use
that to send me staging patches.

Hope this helps,

greg k-h

      reply	other threads:[~2008-12-11 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 19:46 Luis R. Rodriguez
2008-12-11 19:53 ` Greg KH [this message]

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=20081211195325.GA7978@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@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®