Hi Frank,
On Fri, 22 Feb 2008 06:41:00 +0100 Frank Seidel <[EMAIL PROTECTED]> wrote:
>
> Stephen Rothwell wrote:
> > On Fri, 22 Feb 2008 01:07:01 +0100 Frank Seidel <[EMAIL PROTECTED]> wrote:
> >> Hi, i'll provide tars of the current linux-next tree reachable
> >> via my
Hello Stephen,
Stephen Rothwell wrote:
> On Fri, 22 Feb 2008 01:07:01 +0100 Frank Seidel <[EMAIL PROTECTED]> wrote:
>> Hi, i'll provide tars of the current linux-next tree reachable
>> via my http://linux-next.f-seidel.de wiki ("Tar Downloads").
>> Is that what you were looking for?
>
> I was
Greg KH wrote:
> Any reason we can't get these on kernel.org so that the mirror system
> will kick in for the whole world?
Only that i don't have a kernel.org account ;-) But Stephen has and
i suppose he'll put it there.
Thanks,
Frank
--
To unsubscribe from this list: send the line "unsubscribe
Randy Dunlap wrote:
> Looks close. It needs to be scriptable (not just a dynamically generated
> link) and have predictable names. As long as those are true, then it
> should be great.
Yes, i would have scripted it when it tourned out to be of use for others.
But as i just saw Stephen already
Hi Frank,
On Fri, 22 Feb 2008 01:07:01 +0100 Frank Seidel <[EMAIL PROTECTED]> wrote:
>
> Hi, i'll provide tars of the current linux-next tree reachable
> via my http://linux-next.f-seidel.de wiki ("Tar Downloads").
> Is that what you were looking for?
I was going to start providing tarballs
On Thu, 2008-02-21 at 16:12 -0800, Randy Dunlap wrote:
> Frank Seidel wrote:
> > Randy Dunlap wrote:
> >> I'd like to see tarballs too, please...
> >
> > Hi, i'll provide tars of the current linux-next tree reachable
> > via my http://linux-next.f-seidel.de wiki ("Tar Downloads").
> > Is that
On Fri, Feb 22, 2008 at 01:07:01AM +0100, Frank Seidel wrote:
> Randy Dunlap wrote:
> > I'd like to see tarballs too, please...
>
> Hi, i'll provide tars of the current linux-next tree reachable
> via my http://linux-next.f-seidel.de wiki ("Tar Downloads").
> Is that what you were looking for?
Frank Seidel wrote:
Randy Dunlap wrote:
I'd like to see tarballs too, please...
Hi, i'll provide tars of the current linux-next tree reachable
via my http://linux-next.f-seidel.de wiki ("Tar Downloads").
Is that what you were looking for?
Looks close. It needs to be scriptable (not just a
Randy Dunlap wrote:
> I'd like to see tarballs too, please...
Hi, i'll provide tars of the current linux-next tree reachable
via my http://linux-next.f-seidel.de wiki ("Tar Downloads").
Is that what you were looking for?
Thanks,
Frank
--
To unsubscribe from this list: send the line "unsubscribe
Randy Dunlap wrote:
I'd like to see tarballs too, please...
Hi, i'll provide tars of the current linux-next tree reachable
via my http://linux-next.f-seidel.de wiki (Tar Downloads).
Is that what you were looking for?
Thanks,
Frank
--
To unsubscribe from this list: send the line unsubscribe
Frank Seidel wrote:
Randy Dunlap wrote:
I'd like to see tarballs too, please...
Hi, i'll provide tars of the current linux-next tree reachable
via my http://linux-next.f-seidel.de wiki (Tar Downloads).
Is that what you were looking for?
Looks close. It needs to be scriptable (not just a
On Fri, Feb 22, 2008 at 01:07:01AM +0100, Frank Seidel wrote:
Randy Dunlap wrote:
I'd like to see tarballs too, please...
Hi, i'll provide tars of the current linux-next tree reachable
via my http://linux-next.f-seidel.de wiki (Tar Downloads).
Is that what you were looking for?
Any reason
On Thu, 2008-02-21 at 16:12 -0800, Randy Dunlap wrote:
Frank Seidel wrote:
Randy Dunlap wrote:
I'd like to see tarballs too, please...
Hi, i'll provide tars of the current linux-next tree reachable
via my http://linux-next.f-seidel.de wiki (Tar Downloads).
Is that what you were
Hi Frank,
On Fri, 22 Feb 2008 01:07:01 +0100 Frank Seidel [EMAIL PROTECTED] wrote:
Hi, i'll provide tars of the current linux-next tree reachable
via my http://linux-next.f-seidel.de wiki (Tar Downloads).
Is that what you were looking for?
I was going to start providing tarballs yesterday,
Randy Dunlap wrote:
Looks close. It needs to be scriptable (not just a dynamically generated
link) and have predictable names. As long as those are true, then it
should be great.
Yes, i would have scripted it when it tourned out to be of use for others.
But as i just saw Stephen already has
Greg KH wrote:
Any reason we can't get these on kernel.org so that the mirror system
will kick in for the whole world?
Only that i don't have a kernel.org account ;-) But Stephen has and
i suppose he'll put it there.
Thanks,
Frank
--
To unsubscribe from this list: send the line unsubscribe
Hello Stephen,
Stephen Rothwell wrote:
On Fri, 22 Feb 2008 01:07:01 +0100 Frank Seidel [EMAIL PROTECTED] wrote:
Hi, i'll provide tars of the current linux-next tree reachable
via my http://linux-next.f-seidel.de wiki (Tar Downloads).
Is that what you were looking for?
I was going to start
Hi Frank,
On Fri, 22 Feb 2008 06:41:00 +0100 Frank Seidel [EMAIL PROTECTED] wrote:
Stephen Rothwell wrote:
On Fri, 22 Feb 2008 01:07:01 +0100 Frank Seidel [EMAIL PROTECTED] wrote:
Hi, i'll provide tars of the current linux-next tree reachable
via my http://linux-next.f-seidel.de wiki (Tar
On Thu, 21 Feb 2008 01:23:32 +1100 Stephen Rothwell wrote:
> Hi Andy,
>
> On Thu, 14 Feb 2008 16:04:36 + Andy Whitcroft <[EMAIL PROTECTED]> wrote:
> >
> > As devout believers in testing things early we test -mm and -git releases
> > as they drop. I am keen that we are able to continue this
Hi Andy,
On Thu, 14 Feb 2008 16:04:36 + Andy Whitcroft <[EMAIL PROTECTED]> wrote:
>
> As devout believers in testing things early we test -mm and -git releases
> as they drop. I am keen that we are able to continue this with the -next
> tree once it gets going. Having just pulled this tree
Hi Andy,
On Thu, 14 Feb 2008 16:04:36 + Andy Whitcroft [EMAIL PROTECTED] wrote:
As devout believers in testing things early we test -mm and -git releases
as they drop. I am keen that we are able to continue this with the -next
tree once it gets going. Having just pulled this tree its
On Thu, 21 Feb 2008 01:23:32 +1100 Stephen Rothwell wrote:
Hi Andy,
On Thu, 14 Feb 2008 16:04:36 + Andy Whitcroft [EMAIL PROTECTED] wrote:
As devout believers in testing things early we test -mm and -git releases
as they drop. I am keen that we are able to continue this with the
On Fri, 15 Feb 2008 09:24:14 +1100
Stephen Rothwell <[EMAIL PROTECTED]> wrote:
> Hi Mauro,
>
> On Thu, 14 Feb 2008 15:38:50 -0200 Mauro Carvalho Chehab <[EMAIL PROTECTED]>
> wrote:
> >
> > Please add v4l-dvb tree, at:
> >
> >
Hi Paolo,
On Mon, 18 Feb 2008 12:11:33 +0100 "Paolo Ciarrocchi" <[EMAIL PROTECTED]> wrote:
>
> I would like to update the "The development process" section in
> Documentation/HOWTO including some information about the linux-next tree.
>
> I understand what it's including but I didn't get how it
On Feb 14, 2008 2:35 PM, Stephen Rothwell <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have created the first cut of the linux-next tree at
Hi Stephen,
I would like to update the "The development process" section in
Documentation/HOWTO including some information about the linux-next tree.
I
Hi Artem,
On Mon, 18 Feb 2008 10:04:17 +0200 Artem Bityutskiy <[EMAIL PROTECTED]> wrote:
>
> The UBI tree which is here:
>
> git://git.infradead.org/~dedekind/ubi-2.6.git master
Added, thanks.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
pgpeNJ4XqKixk.pgp
Description:
Hi,
Stephen Rothwell wrote:
Also, more trees please ... :-)
The UBI tree which is here:
git://git.infradead.org/~dedekind/ubi-2.6.git master
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Hi,
Stephen Rothwell wrote:
Also, more trees please ... :-)
The UBI tree which is here:
git://git.infradead.org/~dedekind/ubi-2.6.git master
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
Hi Artem,
On Mon, 18 Feb 2008 10:04:17 +0200 Artem Bityutskiy [EMAIL PROTECTED] wrote:
The UBI tree which is here:
git://git.infradead.org/~dedekind/ubi-2.6.git master
Added, thanks.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
pgpeNJ4XqKixk.pgp
Description: PGP
On Feb 14, 2008 2:35 PM, Stephen Rothwell [EMAIL PROTECTED] wrote:
Hi all,
I have created the first cut of the linux-next tree at
Hi Stephen,
I would like to update the The development process section in
Documentation/HOWTO including some information about the linux-next tree.
I understand
Hi Paolo,
On Mon, 18 Feb 2008 12:11:33 +0100 Paolo Ciarrocchi [EMAIL PROTECTED] wrote:
I would like to update the The development process section in
Documentation/HOWTO including some information about the linux-next tree.
I understand what it's including but I didn't get how it will fit in
On Fri, 15 Feb 2008 09:24:14 +1100
Stephen Rothwell [EMAIL PROTECTED] wrote:
Hi Mauro,
On Thu, 14 Feb 2008 15:38:50 -0200 Mauro Carvalho Chehab [EMAIL PROTECTED]
wrote:
Please add v4l-dvb tree, at:
ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git
The
Hi Mark,
On Sun, 17 Feb 2008 14:09:57 -0500 "Mark M. Hoffman" <[EMAIL PROTECTED]> wrote:
>
> You can add the hwmon testing tree (from MAINTAINERS):
>
> > git lm-sensors.org:/kernel/mhoffman/hwmon-2.6.git testing
>
> This tree gets rebased pretty much whenever Linus adds a new tag. As a
> rule
Hi Stephen:
* Stephen Rothwell <[EMAIL PROTECTED]> [2008-02-15 00:35:37 +1100]:
> I have created the first cut of the linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>
> Things to know about this tree:
>
> It has two branches - master and stable. Stable
Hi Stephen:
* Stephen Rothwell [EMAIL PROTECTED] [2008-02-15 00:35:37 +1100]:
I have created the first cut of the linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
Things to know about this tree:
It has two branches - master and stable. Stable is
Hi Mark,
On Sun, 17 Feb 2008 14:09:57 -0500 Mark M. Hoffman [EMAIL PROTECTED] wrote:
You can add the hwmon testing tree (from MAINTAINERS):
git lm-sensors.org:/kernel/mhoffman/hwmon-2.6.git testing
This tree gets rebased pretty much whenever Linus adds a new tag. As a
rule of thumb,
Hi Robin,
On Sat, 16 Feb 2008 21:23:47 -0500 Robin Getz <[EMAIL PROTECTED]> wrote:
>
> You can grab (i386 rpms and tar ball) that should work from:
>
> http://blackfin.uclinux.org/gf/project/toolchain/frs/?action=FrsReleaseView_id=375
>
> You will need:
> - toolchain
On Sat 16 Feb 2008 10:33, Stephen Rothwell pondered:
> On Fri, 15 Feb 2008 16:33:50 +0800 "Bryan Wu" <[EMAIL PROTECTED]> wrote:
> >
> > Could you please add Blackfin tree to the linux-next
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/blackfin-2.6.git
> > for-linus
>
> Added,
On Sat, 16 Feb 2008 16:13:40 +0100 (CET) Stefan Richter <[EMAIL PROTECTED]>
wrote:
>
> Stephen, please add the for-next branch of linux1394-2.6.git to your
> tree to receive updates for drivers/firewire/ and drivers/ieee1394/.
> The URL is
>
>
On Fri, 15 Feb 2008 16:00:57 -0500 "J. Bruce Fields" <[EMAIL PROTECTED]> wrote:
>
> And 'nfsd-next' at
>
> git://git.linux-nfs.org/~bfields/linux.git nfsd-next
Added, thanks.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
pgpflTt6G2U1N.pgp
Description: PGP signature
On Fri, 15 Feb 2008 16:33:50 +0800 "Bryan Wu" <[EMAIL PROTECTED]> wrote:
>
> Could you please add Blackfin tree to the linux-next
>
> git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/blackfin-2.6.git
> for-linus
Added, thanks.
> And do you have the blackfin cross-compile toolchain?
No,
On 15 Feb, Stephen Rothwell wrote at LKML:
> I have created the first cut of the linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>
> Things to know about this tree:
>
> It has two branches - master and stable. Stable is currently just Linus'
> tree and
On Fri, 15 Feb 2008 16:33:50 +0800 Bryan Wu [EMAIL PROTECTED] wrote:
Could you please add Blackfin tree to the linux-next
git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/blackfin-2.6.git
for-linus
Added, thanks.
And do you have the blackfin cross-compile toolchain?
No, I don't at
On 15 Feb, Stephen Rothwell wrote at LKML:
I have created the first cut of the linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
Things to know about this tree:
It has two branches - master and stable. Stable is currently just Linus'
tree and will never
On Sat, 16 Feb 2008 16:13:40 +0100 (CET) Stefan Richter [EMAIL PROTECTED]
wrote:
Stephen, please add the for-next branch of linux1394-2.6.git to your
tree to receive updates for drivers/firewire/ and drivers/ieee1394/.
The URL is
On Fri, 15 Feb 2008 16:00:57 -0500 J. Bruce Fields [EMAIL PROTECTED] wrote:
And 'nfsd-next' at
git://git.linux-nfs.org/~bfields/linux.git nfsd-next
Added, thanks.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
pgpflTt6G2U1N.pgp
Description: PGP signature
On Sat 16 Feb 2008 10:33, Stephen Rothwell pondered:
On Fri, 15 Feb 2008 16:33:50 +0800 Bryan Wu [EMAIL PROTECTED] wrote:
Could you please add Blackfin tree to the linux-next
git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/blackfin-2.6.git
for-linus
Added, thanks.
And do
Hi Robin,
On Sat, 16 Feb 2008 21:23:47 -0500 Robin Getz [EMAIL PROTECTED] wrote:
You can grab (i386 rpms and tar ball) that should work from:
http://blackfin.uclinux.org/gf/project/toolchain/frs/?action=FrsReleaseViewrelease_id=375
You will need:
- toolchain
On Thu, Feb 14, 2008 at 05:27:57PM -0500, Trond Myklebust wrote:
>
> On Fri, 2008-02-15 at 00:35 +1100, Stephen Rothwell wrote:
> >
> > Also, more trees please ... :-)
>
> Please add the 'linux-next' branch of
>
> git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git
And 'nfsd-next' at
On Thu, Feb 14, 2008 at 9:35 PM, Stephen Rothwell <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have created the first cut of the linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>
> Things to know about this tree:
>
> It has two branches - master and stable.
On Thu, Feb 14, 2008 at 9:35 PM, Stephen Rothwell [EMAIL PROTECTED] wrote:
Hi all,
I have created the first cut of the linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
Things to know about this tree:
It has two branches - master and stable. Stable
On Thu, Feb 14, 2008 at 05:27:57PM -0500, Trond Myklebust wrote:
On Fri, 2008-02-15 at 00:35 +1100, Stephen Rothwell wrote:
Also, more trees please ... :-)
Please add the 'linux-next' branch of
git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git
And 'nfsd-next' at
Hi Len,
On Thu, 14 Feb 2008 23:58:38 -0500 Len Brown <[EMAIL PROTECTED]> wrote:
>
> Rafael has it right, please add the branch above.
> It will include both the upcoming ACPI and suspend patches.
Added, thanks, with you as contact.
> Note that I reserve the right to re-base it from time to time
On Thursday 14 February 2008 10:00, Stephen Rothwell wrote:
> Hi Rafael,
>
> On Thu, 14 Feb 2008 15:45:55 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
> wrote:
> >
> > Perhaps you can add:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 test
>
> I would prefer that
Hi David,
On Fri, 15 Feb 2008 12:10:42 +1100 David Chinner <[EMAIL PROTECTED]> wrote:
>
> > I notice that the
> > MAINTAINERS file has a different contact for XFS.
>
> Yup - [EMAIL PROTECTED] If you want a real person
> on the end of problem reports feel free to leave me there,
> but you should
On Fri, Feb 15, 2008 at 11:50:40AM +1100, Stephen Rothwell wrote:
> Hi David,
>
> On Fri, 15 Feb 2008 10:17:02 +1100 David Chinner <[EMAIL PROTECTED]> wrote:
> >
> > The current XFS tree that goes into -mm is:
> >
> > git://oss.sgi.com:8090/xfs/xfs-2.6.git master
>
> Added, thanks.
>
> I have
Hi David,
On Fri, 15 Feb 2008 10:17:02 +1100 David Chinner <[EMAIL PROTECTED]> wrote:
>
> The current XFS tree that goes into -mm is:
>
> git://oss.sgi.com:8090/xfs/xfs-2.6.git master
Added, thanks.
I have put you as the contact point - is this correct? I notice that the
MAINTAINERS file has
Hi Trond,
On Thu, 14 Feb 2008 17:27:57 -0500 Trond Myklebust <[EMAIL PROTECTED]> wrote:
>
> Please add the 'linux-next' branch of
>
> git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git
Added, thanks.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
Hi Jeff,
On Thu, 14 Feb 2008 16:03:19 -0500 Jeff Garzik <[EMAIL PROTECTED]> wrote:
>
> Please add the 'NEXT' branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>
> to your list. This is a throwaway meta-branch that is rebased often.
Added, thanks.
> I will
Hi Sam,
On Thu, 14 Feb 2008 21:50:31 +0100 Sam Ravnborg <[EMAIL PROTECTED]> wrote:
>
> A non-intrusive way to do so would be to add a file in the
> top-level directory and name it localversion*.
>
> For example:
> echo '-next' > localversion-next
Excellent, I will do this for the next release.
Hi Sam,
On Thu, 14 Feb 2008 21:23:23 +0100 Sam Ravnborg <[EMAIL PROTECTED]> wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild.git master
Added, thanks.
> It is rebased from time to time and is what gets into -mm
That's fine.
--
Cheers,
Stephen Rothwell
Hi Greg,
On Thu, 14 Feb 2008 12:20:32 -0800 Greg KH <[EMAIL PROTECTED]> wrote:
>
> Could you change the Makefile to show that if we build and run this
> tree, it really isn't Linus's tree? Yes, I know the -git number will be
> different, but that might not be very obvious to people reading bug
>
On Fri, Feb 15, 2008 at 12:35:37AM +1100, Stephen Rothwell wrote:
> Also, more trees please ... :-)
The current XFS tree that goes into -mm is:
git://oss.sgi.com:8090/xfs/xfs-2.6.git master
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
--
To unsubscribe from
On Fri, 2008-02-15 at 00:35 +1100, Stephen Rothwell wrote:
>
> Also, more trees please ... :-)
Please add the 'linux-next' branch of
git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git
Cheers
Trond
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
Hi Mauro,
On Thu, 14 Feb 2008 15:38:50 -0200 Mauro Carvalho Chehab <[EMAIL PROTECTED]>
wrote:
>
> Please add v4l-dvb tree, at:
>
> ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git
>
> The above tree has two branches: 'master' and 'stable'
>
> Both branches will have
Hi Dave,
On Thu, 14 Feb 2008 09:54:02 -0600 Dave Kleikamp <[EMAIL PROTECTED]> wrote:
>
> Please add:
> git://git.kernel.org/pub/scm/linux/kernel/git/shaggy/jfs-2.6.git next
Added, thanks.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
http://www.canb.auug.org.au/~sfr/
Hi Paul,
On Fri, 15 Feb 2008 00:49:28 +0900 Paul Mundt <[EMAIL PROTECTED]> wrote:
>
> For SH:
>
> master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.git
Added, thanks.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
http://www.canb.auug.org.au/~sfr/
Hi Martin,
On Thu, 14 Feb 2008 16:25:09 +0100 Martin Schwidefsky <[EMAIL PROTECTED]> wrote:
>
> For the s390 architecture please use the "features" branch of git390:
>
> git://git390.osdl.marist.edu/pub/scm/linux-2.6.git features
Added thanks.
--
Cheers,
Stephen Rothwell
James Bottomley wrote:
So does this indicate the meaning of upstream and upstream-fixes is
still the same? I always took upstream-fixes to be bug fixes for this
-rc and upstream as queued for the next merge window, in which case NEXT
would be the union of those two sets?
In practice,
On Thu, 2008-02-14 at 16:03 -0500, Jeff Garzik wrote:
> Stephen Rothwell wrote:
> > Also, more trees please ... :-)
>
> Please add the 'NEXT' branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>
> to your list. This is a throwaway meta-branch that is rebased
Jeff Garzik wrote:
Please add the 'NEXT' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
to your list. This is a throwaway meta-branch that is rebased often.
Additional FYI:
Don't be worried if "git diff master..NEXT" is empty from time to time.
This
Stephen Rothwell wrote:
Also, more trees please ... :-)
Please add the 'NEXT' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
to your list. This is a throwaway meta-branch that is rebased often.
The 'master' branch of libata-dev.git always contains the base
On Thu, Feb 14, 2008 at 12:20:32PM -0800, Greg KH wrote:
> On Fri, Feb 15, 2008 at 12:35:37AM +1100, Stephen Rothwell wrote:
> >
> > So, comments, please.
>
> Could you change the Makefile to show that if we build and run this
> tree, it really isn't Linus's tree? Yes, I know the -git number
>
> Also, more trees please ... :-)
git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild.git master
It is rebased from time to time and is what gets into -mm
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Fri, Feb 15, 2008 at 12:35:37AM +1100, Stephen Rothwell wrote:
>
> So, comments, please.
Could you change the Makefile to show that if we build and run this
tree, it really isn't Linus's tree? Yes, I know the -git number will be
different, but that might not be very obvious to people reading
On Feb. 14, 2008, 20:29 +0200, "Yinghai Lu" <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 14, 2008 at 5:35 AM, Stephen Rothwell <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> I have created the first cut of the linux-next tree at
>> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>>
>>
On Thu, Feb 14, 2008 at 5:35 AM, Stephen Rothwell <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I have created the first cut of the linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>
> Things to know about this tree:
>
> It has two branches - master and stable.
> The tree currently contains:
> Greg's driver-core, pci and usb quilt series (in that order)
> Alasdair Kergon's device-mapper quilt tree
> Jiri Kosina's hid git tree
> Jean Delvare's i2c quilt tree
> Randy Dunlap's kernel-doc quilt tree
> Haavard Skinnemoen's
On Fri, Feb 15, 2008 at 12:35:37AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> I have created the first cut of the linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>
> Things to know about this tree:
>
> It has two branches - master and stable. Stable is
On Fri, 2008-02-15 at 02:00 +1100, Stephen Rothwell wrote:
> I would prefer that the trees be added by the subsystem maintainers and
> they can tell me which branch represents their expectations for the next
> kernel release (in this case 2.6.26). But thanks, hopefully you will have
> prodded
On Fri, Feb 15, 2008 at 02:00:19AM +1100, Stephen Rothwell wrote:
> Hi Rafael,
>
> On Thu, 14 Feb 2008 15:45:55 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
> wrote:
> >
> > Perhaps you can add:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 test
>
> I would prefer
On Fri, 2008-02-15 at 02:00 +1100, Stephen Rothwell wrote:
> I would prefer that the trees be added by the subsystem maintainers and
> they can tell me which branch represents their expectations for the next
> kernel release (in this case 2.6.26). But thanks, hopefully you will have
> prodded them
Hi Rafael,
On Thu, 14 Feb 2008 15:45:55 +0100 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
wrote:
>
> Perhaps you can add:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 test
I would prefer that the trees be added by the subsystem maintainers and
they can tell me which branch
On Thursday, 14 of February 2008, Stephen Rothwell wrote:
> Hi all,
>
> I have created the first cut of the linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
>
> Things to know about this tree:
>
> It has two branches - master and stable. Stable is
On Thu, 14 Feb 2008 15:06:28 +0100 (CET) Jiri Kosina <[EMAIL PROTECTED]> wrote:
>
> On Fri, 15 Feb 2008, Stephen Rothwell wrote:
>
> > The tree consists of subsystem git and quilt trees. Currently, the
> > quilt trees are integrated by importing them into appropriately based
> > git branches
On Fri, 15 Feb 2008, Stephen Rothwell wrote:
> The tree consists of subsystem git and quilt trees. Currently, the
> quilt trees are integrated by importing them into appropriately based
> git branches and then merging those branches.
Now, would it be possible to have somewhere listed the
Hi all,
I have created the first cut of the linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
Things to know about this tree:
It has two branches - master and stable. Stable is currently just Linus'
tree and will never rebase. Master will rebase on an almost
On Thu, 14 Feb 2008 15:06:28 +0100 (CET) Jiri Kosina [EMAIL PROTECTED] wrote:
On Fri, 15 Feb 2008, Stephen Rothwell wrote:
The tree consists of subsystem git and quilt trees. Currently, the
quilt trees are integrated by importing them into appropriately based
git branches and then
On Thursday, 14 of February 2008, Stephen Rothwell wrote:
Hi all,
I have created the first cut of the linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
Things to know about this tree:
It has two branches - master and stable. Stable is currently just
Hi Rafael,
On Thu, 14 Feb 2008 15:45:55 +0100 Rafael J. Wysocki [EMAIL PROTECTED]
wrote:
Perhaps you can add:
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 test
I would prefer that the trees be added by the subsystem maintainers and
they can tell me which branch
On Fri, 2008-02-15 at 02:00 +1100, Stephen Rothwell wrote:
I would prefer that the trees be added by the subsystem maintainers and
they can tell me which branch represents their expectations for the next
kernel release (in this case 2.6.26). But thanks, hopefully you will have
prodded them
On Fri, Feb 15, 2008 at 02:00:19AM +1100, Stephen Rothwell wrote:
Hi Rafael,
On Thu, 14 Feb 2008 15:45:55 +0100 Rafael J. Wysocki [EMAIL PROTECTED]
wrote:
Perhaps you can add:
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 test
I would prefer that the trees be
On Fri, 2008-02-15 at 02:00 +1100, Stephen Rothwell wrote:
I would prefer that the trees be added by the subsystem maintainers and
they can tell me which branch represents their expectations for the next
kernel release (in this case 2.6.26). But thanks, hopefully you will have
prodded them
On Fri, Feb 15, 2008 at 12:35:37AM +1100, Stephen Rothwell wrote:
Hi all,
I have created the first cut of the linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
Things to know about this tree:
It has two branches - master and stable. Stable is
The tree currently contains:
Greg's driver-core, pci and usb quilt series (in that order)
Alasdair Kergon's device-mapper quilt tree
Jiri Kosina's hid git tree
Jean Delvare's i2c quilt tree
Randy Dunlap's kernel-doc quilt tree
Haavard Skinnemoen's avr32
On Thu, Feb 14, 2008 at 5:35 AM, Stephen Rothwell [EMAIL PROTECTED] wrote:
Hi all,
I have created the first cut of the linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
Things to know about this tree:
It has two branches - master and stable. Stable
On Feb. 14, 2008, 20:29 +0200, Yinghai Lu [EMAIL PROTECTED] wrote:
On Thu, Feb 14, 2008 at 5:35 AM, Stephen Rothwell [EMAIL PROTECTED] wrote:
Hi all,
I have created the first cut of the linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
Things to know
Also, more trees please ... :-)
git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild.git master
It is rebased from time to time and is what gets into -mm
Sam
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
On Fri, Feb 15, 2008 at 12:35:37AM +1100, Stephen Rothwell wrote:
So, comments, please.
Could you change the Makefile to show that if we build and run this
tree, it really isn't Linus's tree? Yes, I know the -git number will be
different, but that might not be very obvious to people reading
Stephen Rothwell wrote:
Also, more trees please ... :-)
Please add the 'NEXT' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
to your list. This is a throwaway meta-branch that is rebased often.
The 'master' branch of libata-dev.git always contains the base
1 - 100 of 119 matches
Mail list logo
