Skip to contentSkip to conversation

linux-next fixes

DISCUSSION Thierry Reding 2 participants 4 messages Nov 1, 2013 – Nov 4, 2013 1 message not in the archive Linux-next tree

lore
Share & tools
lore
#0 lore raw

Hi Stephen,

There have been some discussions lately revolving around the topic of linux-next fixes. That is, commits that people come up with over the course of a day to fix issues found in the latest linux-next trees.

It's a fact that many people rely on linux-next for everyday work, so whenever things break in linux-next a lot of people end up chasing the same bugs and posting the same patches (or not posting them for that matter).

A lot of developer time is wasted that way, so I originally proposed that we could set up a separate linux-next-fixes tree where we collect patches of interest. I volunteer to do that, since, well, I'm doing it anyway as part of my daily routine. Timezone-wise it also fits pretty well, since I usually start my day sometime around when you publish linux-next.

If we can establish a canonical location where such fixes are accumulated, people could fetch those at the same time they fetch the linux-next tree and automatically get fixes.

One idea was to carry those fixes within the linux-next tree, within separate tags (next-YYYYMMDD-fixes). If you don't feel comfortable with that I suppose we could also set up a separate repository. It that case I think it would still make sense to run it as part of the "Linux Next Group" on kernel.org.

What do you think? If it's something you'd be okay with I can contact the administrators to have me added to the linux-next group.

Thierry

#1 lore raw
Quoted 18 lines · Thierry Reding

Hi Stephen,

There have been some discussions lately revolving around the topic of linux-next fixes. That is, commits that people come up with over the course of a day to fix issues found in the latest linux-next trees.

It's a fact that many people rely on linux-next for everyday work, so whenever things break in linux-next a lot of people end up chasing the same bugs and posting the same patches (or not posting them for that matter).

A lot of developer time is wasted that way, so I originally proposed that we could set up a separate linux-next-fixes tree where we collect patches of interest. I volunteer to do that, since, well, I'm doing it anyway as part of my daily routine. Timezone-wise it also fits pretty well, since I usually start my day sometime around when you publish linux-next.

Quoted 3 lines

If we can establish a canonical location where such fixes are accumulated, people could fetch those at the same time they fetch the linux-next tree and automatically get fixes.

Stephen has had a location for linux-next fixes for quite some time now -- in the linux-next tree itself.

Apparently Olof objected to this and you agreed with him. and I object to not having the fixes in the linux-next tree. Maybe Stephen can work it out. :)

Quoted 8 lines

One idea was to carry those fixes within the linux-next tree, within separate tags (next-YYYYMMDD-fixes). If you don't feel comfortable with that I suppose we could also set up a separate repository. It that case I think it would still make sense to run it as part of the "Linux Next Group" on kernel.org.

What do you think? If it's something you'd be okay with I can contact the administrators to have me added to the linux-next group.

Signature · 1 line
~Randy
#2 lore raw
Quoted 23 lines · Randy Dunlap
Quoted 18 lines · Thierry Reding

Hi Stephen,

There have been some discussions lately revolving around the topic of linux-next fixes. That is, commits that people come up with over the course of a day to fix issues found in the latest linux-next trees.

It's a fact that many people rely on linux-next for everyday work, so whenever things break in linux-next a lot of people end up chasing the same bugs and posting the same patches (or not posting them for that matter).

A lot of developer time is wasted that way, so I originally proposed that we could set up a separate linux-next-fixes tree where we collect patches of interest. I volunteer to do that, since, well, I'm doing it anyway as part of my daily routine. Timezone-wise it also fits pretty well, since I usually start my day sometime around when you publish linux-next.

Quoted 3 lines

If we can establish a canonical location where such fixes are accumulated, people could fetch those at the same time they fetch the linux-next tree and automatically get fixes.

Quoted 5 lines

Stephen has had a location for linux-next fixes for quite some time now -- in the linux-next tree itself.

Apparently Olof objected to this and you agreed with him. and I object to not having the fixes in the linux-next tree.

What I did agree to was a compromise. I do see some sense in not carrying all the fixes in linux-next so that the actual state of brokenness is reflected.

But I also think that for everyone using linux-next for daily work it makes sense to have these patches in a central location in order to minimize duplicate work.

Quoted 1 line

Maybe Stephen can work it out. :)

If nobody wants to have this in linux-next itself, then I still plan on maintaining a tree for myself so that people that work in the same areas in a later timezone don't have to duplicate all of that.

Thierry

#4 lore raw
In reply to a message not in the archive
Quoted 32 lines · Olof Johansson
Quoted 24 lines · Randy Dunlap
Quoted 18 lines · Thierry Reding

Hi Stephen,

There have been some discussions lately revolving around the topic of linux-next fixes. That is, commits that people come up with over the course of a day to fix issues found in the latest linux-next trees.

It's a fact that many people rely on linux-next for everyday work, so whenever things break in linux-next a lot of people end up chasing the same bugs and posting the same patches (or not posting them for that matter).

A lot of developer time is wasted that way, so I originally proposed that we could set up a separate linux-next-fixes tree where we collect patches of interest. I volunteer to do that, since, well, I'm doing it anyway as part of my daily routine. Timezone-wise it also fits pretty well, since I usually start my day sometime around when you publish linux-next.

Quoted 3 lines

If we can establish a canonical location where such fixes are accumulated, people could fetch those at the same time they fetch the linux-next tree and automatically get fixes.

Quoted 6 lines

Stephen has had a location for linux-next fixes for quite some time now -- in the linux-next tree itself.

Apparently Olof objected to this and you agreed with him. and I object to not having the fixes in the linux-next tree. Maybe Stephen can work it out. :)

Quoted 5 lines

My main concern was that they stacked up quickly for a while and had no patch descriptions in -next. It does make sense to carry some if these patches somewhere. Normally we haven't needed many though, and if we do then that's a pretty strong indication that people are adding code to their for-next that is not yet ready and that should be addressed.

Oh, it would certainly be desirable for such patches to be unnecessary, but the reality is that this will happen every now and then. Sometimes this will not even be detectable as build failures. A lot of patches recently haven't broken the build but instead caused a random board (that the commit author didn't have access to, or was just too lazy to test) to no longer boot.

One of the purposes of linux-next is to get early and broad testing, isn't it? So I don't expect code to be rock-stable when it hits -next.

Thierry