git: Sync zoneinfo database with tzdata2010g from elsie.
saw at online.de
Mon Mar 29 14:30:15 PDT 2010
Am 29.03.2010 23:19, schrieb Matthew Dillon:
:So how will we distinguish between stuff intended for 2.6 and stuff
:which is not (such as my 771006e11a2e17275d714eb2290fa84c3035cec4)?
:Or does it imply that commits not intended for 2.6 should be held off
:IMO each committer can easily care about MFC themselves since it's
:really quite easy with git cherry-pick.
I was just going to run through them to see what is applicable,
maybe it's a bad idea ? :-)
Nono, I was just asking what our general procedure is here for the time
when we already branched but haven't yet officially released. I can live
Just do as you intended. :) Actually, there should be no harm if the
syscons commit goes into 2.6 anyway. I'm fairly certain there aren't any
bugs left, and the user won't hit the new code unless they switch to one
of these modes.
More information about the Commits