[Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-24 Thread Konstantin Ryabitsev via RT
On 2017-05-24 14:42:54, li...@nerdbynature.de wrote: > > We are trying to identify who are the people who still need to > > download > > patches as opposed to using git directly, and what their use-case > > I never use the links on the kernel.org main page to download patches, > but > still: can

[Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-24 Thread Konstantin Ryabitsev via RT
On 2017-05-24 14:42:54, li...@nerdbynature.de wrote: > > We are trying to identify who are the people who still need to > > download > > patches as opposed to using git directly, and what their use-case > > I never use the links on the kernel.org main page to download patches, > but > still: can

Re: [Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-24 Thread Christian Kujau via RT
On Mon, 15 May 2017, Konstantin Ryabitsev via RT wrote: > On 2017-05-15 14:34:56, francoisvalen...@gmail.com wrote: > > It doesn't work with Firefox-53.0. After quite a long time while > > firefox > > uses 100% of CPU, I finally get a text file and not a gzip file of the > > patch for 4.12-rc1. It

Re: [Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-24 Thread Christian Kujau via RT
On Mon, 15 May 2017, Konstantin Ryabitsev via RT wrote: > On 2017-05-15 14:34:56, francoisvalen...@gmail.com wrote: > > It doesn't work with Firefox-53.0. After quite a long time while > > firefox > > uses 100% of CPU, I finally get a text file and not a gzip file of the > > patch for 4.12-rc1. It

Re: [Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-24 Thread Christian Kujau
On Mon, 15 May 2017, Konstantin Ryabitsev via RT wrote: > On 2017-05-15 14:34:56, francoisvalen...@gmail.com wrote: > > It doesn't work with Firefox-53.0. After quite a long time while > > firefox > > uses 100% of CPU, I finally get a text file and not a gzip file of the > > patch for 4.12-rc1. It

Re: [Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-24 Thread Christian Kujau
On Mon, 15 May 2017, Konstantin Ryabitsev via RT wrote: > On 2017-05-15 14:34:56, francoisvalen...@gmail.com wrote: > > It doesn't work with Firefox-53.0. After quite a long time while > > firefox > > uses 100% of CPU, I finally get a text file and not a gzip file of the > > patch for 4.12-rc1. It

Re: linux-next: stats (Was: Linux 4.12-rc1)

2017-05-20 Thread Sebastian Reichel
Hi Stephen, On Tue, May 16, 2017 at 07:32:09AM +1000, Stephen Rothwell wrote: > On Mon, 15 May 2017 16:51:08 +0200 Sebastian Reichel wrote: > > On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote: > > > There are also 288 commits in next-20170502 that didn't make it

Re: linux-next: stats (Was: Linux 4.12-rc1)

2017-05-20 Thread Sebastian Reichel
Hi Stephen, On Tue, May 16, 2017 at 07:32:09AM +1000, Stephen Rothwell wrote: > On Mon, 15 May 2017 16:51:08 +0200 Sebastian Reichel wrote: > > On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote: > > > There are also 288 commits in next-20170502 that didn't make it into > > >

[Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-16 Thread Konstantin Ryabitsev via RT
On 2017-05-15 11:42:48, torva...@linux-foundation.org wrote: > so the capability is there, it's just not done as several individual > files any more. I've published a news item explaining the new process and the reasoning behind not providing these automatically generated tarballs and patches as

[Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-16 Thread Konstantin Ryabitsev via RT
On 2017-05-15 11:42:48, torva...@linux-foundation.org wrote: > so the capability is there, it's just not done as several individual > files any more. I've published a news item explaining the new process and the reasoning behind not providing these automatically generated tarballs and patches as

Re: linux-next: stats (Was: Linux 4.12-rc1)

2017-05-15 Thread Stephen Rothwell
Hi Sebastian, On Mon, 15 May 2017 16:51:08 +0200 Sebastian Reichel wrote: > > On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote: > > There are also 288 commits in next-20170502 that didn't make it into > > v4.12-rc1. > > > > [...] > > > > Top ten commiters: > >

Re: linux-next: stats (Was: Linux 4.12-rc1)

2017-05-15 Thread Stephen Rothwell
Hi Sebastian, On Mon, 15 May 2017 16:51:08 +0200 Sebastian Reichel wrote: > > On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote: > > There are also 288 commits in next-20170502 that didn't make it into > > v4.12-rc1. > > > > [...] > > > > Top ten commiters: > > > > 66

[Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread Konstantin Ryabitsev via RT
On 2017-05-14 13:59:22, rdun...@infradead.org wrote: > On 05/13/17 13:57, Linus Torvalds wrote: > > One thing worth noting - I haven't uploaded diffs or tar-balls for > > this rc. Those should now be automagically generated by kernel.org for > > the rc's, but that also means that they won't be

[Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread Konstantin Ryabitsev via RT
On 2017-05-14 13:59:22, rdun...@infradead.org wrote: > On 05/13/17 13:57, Linus Torvalds wrote: > > One thing worth noting - I haven't uploaded diffs or tar-balls for > > this rc. Those should now be automagically generated by kernel.org for > > the rc's, but that also means that they won't be

[Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread Konstantin Ryabitsev via RT
On 2017-05-15 14:34:56, francoisvalen...@gmail.com wrote: > It doesn't work with Firefox-53.0. After quite a long time while > firefox > uses 100% of CPU, I finally get a text file and not a gzip file of the > patch for 4.12-rc1. It was almost instantaneous previously. I don't > see > this as a

[Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread Konstantin Ryabitsev via RT
On 2017-05-15 14:34:56, francoisvalen...@gmail.com wrote: > It doesn't work with Firefox-53.0. After quite a long time while > firefox > uses 100% of CPU, I finally get a text file and not a gzip file of the > patch for 4.12-rc1. It was almost instantaneous previously. I don't > see > this as a

Re: [Kernel.org Helpdesk #40777] [linuxfoundation.org #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread François Valenduc
Le 15/05/17 à 17:42, Linus Torvalds via RT a écrit : > On Sun, May 14, 2017 at 10:59 AM, Randy Dunlap wrote: >> >> Can the generated files please be put in the same places that (most or >> all) previous releases have used? > > I will leave this to Konstantin.. There may

Re: [Kernel.org Helpdesk #40777] [linuxfoundation.org #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread François Valenduc via RT
Le 15/05/17 à 17:42, Linus Torvalds via RT a écrit : > On Sun, May 14, 2017 at 10:59 AM, Randy Dunlap wrote: >> >> Can the generated files please be put in the same places that (most or >> all) previous releases have used? > > I will leave this to Konstantin.. There may

Re: [Kernel.org Helpdesk #40777] [linuxfoundation.org #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread François Valenduc
Le 15/05/17 à 17:42, Linus Torvalds via RT a écrit : > On Sun, May 14, 2017 at 10:59 AM, Randy Dunlap wrote: >> >> Can the generated files please be put in the same places that (most or >> all) previous releases have used? > > I will leave this to Konstantin.. There may well be practical reasons

Re: [Kernel.org Helpdesk #40777] [linuxfoundation.org #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread François Valenduc via RT
Le 15/05/17 à 17:42, Linus Torvalds via RT a écrit : > On Sun, May 14, 2017 at 10:59 AM, Randy Dunlap wrote: >> >> Can the generated files please be put in the same places that (most or >> all) previous releases have used? > > I will leave this to Konstantin.. There may well be practical reasons

[Kernel.org Helpdesk #40777] [linuxfoundation.org #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread Linus Torvalds via RT
On Sun, May 14, 2017 at 10:59 AM, Randy Dunlap wrote: > > Can the generated files please be put in the same places that (most or > all) previous releases have used? I will leave this to Konstantin.. There may well be practical reasons for the movement. > Oh, and the patch

[Kernel.org Helpdesk #40777] [linuxfoundation.org #40777] Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread Linus Torvalds via RT
On Sun, May 14, 2017 at 10:59 AM, Randy Dunlap wrote: > > Can the generated files please be put in the same places that (most or > all) previous releases have used? I will leave this to Konstantin.. There may well be practical reasons for the movement. > Oh, and the patch file (on

Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread Linus Torvalds
On Sun, May 14, 2017 at 10:59 AM, Randy Dunlap wrote: > > Can the generated files please be put in the same places that (most or > all) previous releases have used? I will leave this to Konstantin.. There may well be practical reasons for the movement. > Oh, and the patch

Re: Linux 4.12-rc1 (file locations)

2017-05-15 Thread Linus Torvalds
On Sun, May 14, 2017 at 10:59 AM, Randy Dunlap wrote: > > Can the generated files please be put in the same places that (most or > all) previous releases have used? I will leave this to Konstantin.. There may well be practical reasons for the movement. > Oh, and the patch file (on

Re: linux-next: stats (Was: Linux 4.12-rc1)

2017-05-15 Thread Sebastian Reichel
Hi, On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote: > There are also 288 commits in next-20170502 that didn't make it into > v4.12-rc1. > > [...] > > Top ten commiters: > > 66 s...@canb.auug.org.au > 47 paul...@linux.vnet.ibm.com > 34 t...@linutronix.de >

Re: linux-next: stats (Was: Linux 4.12-rc1)

2017-05-15 Thread Sebastian Reichel
Hi, On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote: > There are also 288 commits in next-20170502 that didn't make it into > v4.12-rc1. > > [...] > > Top ten commiters: > > 66 s...@canb.auug.org.au > 47 paul...@linux.vnet.ibm.com > 34 t...@linutronix.de >

linux-next: stats (Was: Linux 4.12-rc1)

2017-05-15 Thread Stephen Rothwell
Hi all, As usual, the executive friendly graph is at http://neuling.org/linux-next-size.html :-) (No merge commits counted, next-20170502 was the first linux-next after the merge window opened.) Commits in v4.12-rc1 (relative to v4.11): 12920 Commits in next-20170502:

linux-next: stats (Was: Linux 4.12-rc1)

2017-05-15 Thread Stephen Rothwell
Hi all, As usual, the executive friendly graph is at http://neuling.org/linux-next-size.html :-) (No merge commits counted, next-20170502 was the first linux-next after the merge window opened.) Commits in v4.12-rc1 (relative to v4.11): 12920 Commits in next-20170502:

Re: Linux 4.12-rc1 (file locations)

2017-05-14 Thread Randy Dunlap
On 05/13/17 13:57, Linus Torvalds wrote: > One thing worth noting - I haven't uploaded diffs or tar-balls for > this rc. Those should now be automagically generated by kernel.org for > the rc's, but that also means that they won't be signed by my key. If > you really care about signing, get the

Re: Linux 4.12-rc1 (file locations)

2017-05-14 Thread Randy Dunlap
On 05/13/17 13:57, Linus Torvalds wrote: > One thing worth noting - I haven't uploaded diffs or tar-balls for > this rc. Those should now be automagically generated by kernel.org for > the rc's, but that also means that they won't be signed by my key. If > you really care about signing, get the

Linux 4.12-rc1

2017-05-13 Thread Linus Torvalds
So I'm doing this one day early, because I don't like last-minute pull requests during the merge window anyway, and tomorrow is mother's day, so I may end up being roped into various happenings. Besides, this has actually been a pretty large merge window, so despite there technically being time

Linux 4.12-rc1

2017-05-13 Thread Linus Torvalds
So I'm doing this one day early, because I don't like last-minute pull requests during the merge window anyway, and tomorrow is mother's day, so I may end up being roped into various happenings. Besides, this has actually been a pretty large merge window, so despite there technically being time