* What version should I be patching against?
@ 2013-07-30 4:26 Dolan Murvihill
2013-07-30 8:53 ` Dan Carpenter
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: Dolan Murvihill @ 2013-07-30 4:26 UTC (permalink / raw)
To: kernel-janitors
Q: What version should I be patching against?
I saw this answer in the FAQ on https://code.google.com/p/kernel-janitors/ :
A: Latest "linus" (2.6.x-rcY from kernel.org).
Two questions about this:
1. Is this still current? My understanding was that we moved past 2.6
long ago, and any changes would be ported from the latest 3.x release.
2. Did you mean "torvalds", or is there another tree called "linus"?
For now, I'm going to work with Linus' tree at
pub/scm/linux/kernel/git/torvalds/linux.git.
-Dolan
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: What version should I be patching against?
2013-07-30 4:26 What version should I be patching against? Dolan Murvihill
@ 2013-07-30 8:53 ` Dan Carpenter
2013-07-30 9:35 ` Nikola Pajkovsky
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Dan Carpenter @ 2013-07-30 8:53 UTC (permalink / raw)
To: kernel-janitors
Wow... Yes. That information is totally out of date. Do patches
against the daily linux-next. Don't do them against mainline.
regards,
dan carpenter
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: What version should I be patching against?
2013-07-30 4:26 What version should I be patching against? Dolan Murvihill
2013-07-30 8:53 ` Dan Carpenter
@ 2013-07-30 9:35 ` Nikola Pajkovsky
2013-07-30 13:40 ` Shaun Laing
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Nikola Pajkovsky @ 2013-07-30 9:35 UTC (permalink / raw)
To: kernel-janitors
Dan Carpenter <dan.carpenter@oracle.com> writes:
> Wow... Yes. That information is totally out of date. Do patches
> against the daily linux-next. Don't do them against mainline.
these commands would be useful to add
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
$ git fetch linux-next
$ git fetch --tags linux-next
... # later on
$ git remote update
...
--
Nikola
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: What version should I be patching against?
2013-07-30 4:26 What version should I be patching against? Dolan Murvihill
2013-07-30 8:53 ` Dan Carpenter
2013-07-30 9:35 ` Nikola Pajkovsky
@ 2013-07-30 13:40 ` Shaun Laing
2013-07-30 14:36 ` Laurent Navet
2013-07-30 19:13 ` Dan Carpenter
4 siblings, 0 replies; 6+ messages in thread
From: Shaun Laing @ 2013-07-30 13:40 UTC (permalink / raw)
To: kernel-janitors
That's really good information, thank you.
Dan, I recently submitted a patch and the message back was:
"This is a note to let you know that I've just added the patch titled
staging: comedi: dt9812: Resolves sparse endian warnings.
to my staging git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
in the staging-next branch.
"
Is it wrong to be patching against this
(git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git),
then? (I also see a reference to this at
https://code.google.com/p/kernel-janitors/wiki/TODO under
"Linux-Staging Tree").
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: What version should I be patching against?
2013-07-30 4:26 What version should I be patching against? Dolan Murvihill
` (2 preceding siblings ...)
2013-07-30 13:40 ` Shaun Laing
@ 2013-07-30 14:36 ` Laurent Navet
2013-07-30 19:13 ` Dan Carpenter
4 siblings, 0 replies; 6+ messages in thread
From: Laurent Navet @ 2013-07-30 14:36 UTC (permalink / raw)
To: kernel-janitors
> Dan, I recently submitted a patch and the message back was:
>
> "This is a note to let you know that I've just added the patch titled
>
> staging: comedi: dt9812: Resolves sparse endian warnings.
>
> to my staging git tree which can be found at
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> in the staging-next branch.
Congratulations,
This is a message from Greg Kroah-Hartman workflow, your patch will be
part of the next kernel release (3.12).
--
« On ne résout pas un problème avec les modes de pensée qui l’ont engendré. »
« You cannot solve current problems with current thinking. Current
problems are the result of current thinking »
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: What version should I be patching against?
2013-07-30 4:26 What version should I be patching against? Dolan Murvihill
` (3 preceding siblings ...)
2013-07-30 14:36 ` Laurent Navet
@ 2013-07-30 19:13 ` Dan Carpenter
4 siblings, 0 replies; 6+ messages in thread
From: Dan Carpenter @ 2013-07-30 19:13 UTC (permalink / raw)
To: kernel-janitors
On Tue, Jul 30, 2013 at 07:40:38AM -0600, Shaun Laing wrote:
> That's really good information, thank you.
>
> Dan, I recently submitted a patch and the message back was:
>
> "This is a note to let you know that I've just added the patch titled
>
> staging: comedi: dt9812: Resolves sparse endian warnings.
>
> to my staging git tree which can be found at
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> in the staging-next branch.
> "
>
> Is it wrong to be patching against this
> (git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git),
> then? (I also see a reference to this at
> https://code.google.com/p/kernel-janitors/wiki/TODO under
> "Linux-Staging Tree").
Stephen Rothwell creates linux-next daily. He takes everyone's
development trees and merges them.
regards,
dan carpenter
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-07-30 19:13 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-30 4:26 What version should I be patching against? Dolan Murvihill
2013-07-30 8:53 ` Dan Carpenter
2013-07-30 9:35 ` Nikola Pajkovsky
2013-07-30 13:40 ` Shaun Laing
2013-07-30 14:36 ` Laurent Navet
2013-07-30 19:13 ` Dan Carpenter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox