Skip to contentSkip to conversation

libata-dev.git frozen

DISCUSSION Jeff Garzik 2 participants 2 messages Oct 1, 2006 – Oct 2, 2006 1 message not in the archive libata

lore
Share & tools
lore
#0 lore raw

Similar to the netdev announcement, libata-dev.git is now closed to new features.

Though really, [my fault] I should have posted this as soon as the merge window opened. The stuff that goes into each new release, when the merge window opens, should be stuff that has already been through a round of testing in -mm.

The updates presented in #upstream -- just minor stuff, really -- will go upstream tomorrow. Everything else will be fixes.

And the message for the future is: don't wait until the merge window opens, to submit your code. Doing so means it doesn't get the normal amount of testing and review, and is thus discouraged.

Jeff

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 29 lines · Uwe Koziolek

Hi Jeff

I have sent to you a patch for sata_sis withsis966 before the frozen statement. But i have got no feedback from you. reject ? acknowledged for 2.6.20?
What must I do?.

regards,
Uwe Koziolek

Quoted 17 lines · Jeff Garzik

Similar to the netdev announcement, libata-dev.git is now closed to new features.

Though really, [my fault] I should have posted this as soon as the merge window opened. The stuff that goes into each new release, when the merge window opens, should be stuff that has already been through a round of testing in -mm.

The updates presented in #upstream -- just minor stuff, really -- will go upstream tomorrow. Everything else will be fixes.

And the message for the future is: don't wait until the merge window opens, to submit your code. Doing so means it doesn't get the normal amount of testing and review, and is thus discouraged.

Jeff