Skip to contentSkip to conversation

Regarding the l2-mtd branch in linux-next

DISCUSSION Ezequiel Garcia 2 participants 3 messages Nov 20, 2013

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Brian,

Can you explain in detail the differences between l2-mtd/master and l2-mtd/next?

I'm seeing linux-next merges the former, but instead maybe it should be the latter?

What do you think?

Signature · 3 lines
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
#1 lore raw

Hi Ezequiel,

Quoted 7 lines · Ezequiel Garcia

Can you explain in detail the differences between l2-mtd/master and l2-mtd/next?

I'm seeing linux-next merges the former, but instead maybe it should be the latter?

What do you think?

I only created the l2-mtd.git 'next' branch recently because I don't think linux-next likes to see new stuff during the merge window that's not going into the current release cycle. So I just queued up stuff in a different branch temporarily, and I plan to bring it into 'master' on top of 3.13-rc1 once the merge window closes.

In answer to your second question, then, the inclusion of l2-mtd.git/master in linux-next is exactly as intended.

I am new at this whole maintainership thing, though, and I could be very wrong about the intended development process regarding linux-next and the merge window. I couldn't find much clear documentation regarding this process. I suppose it's something you learn over time. Any comments are welcome.

Regards,
Brian

#2 lore raw
Quoted 17 lines · Brian Norris

Hi Ezequiel,

Quoted 7 lines · Ezequiel Garcia

Can you explain in detail the differences between l2-mtd/master and l2-mtd/next?

I'm seeing linux-next merges the former, but instead maybe it should be the latter?

What do you think?

I only created the l2-mtd.git 'next' branch recently because I don't think linux-next likes to see new stuff during the merge window that's not going into the current release cycle. So I just queued up stuff in a different branch temporarily, and I plan to bring it into 'master' on top of 3.13-rc1 once the merge window closes.

Quoted 9 lines

In answer to your second question, then, the inclusion of l2-mtd.git/master in linux-next is exactly as intended.

I am new at this whole maintainership thing, though, and I could be very wrong about the intended development process regarding linux-next and the merge window. I couldn't find much clear documentation regarding this process. I suppose it's something you learn over time. Any comments are welcome.

Hm, I see. Well, I'm not an expert but the above sounds just about the right thing to do.

Sorry for the noise!

Signature · 3 lines
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com