Lines Matching refs:it

35 Q: How often do changes from these trees make it to the mainline Linus tree?
41    the merge window is closed, and it is called/tagged "-rc1".  No new
81    and note the top of the "tags" section.  If it is rc1, it is early
82    in the dev cycle.  If it was tagged rc7 a week ago, then a release
95    manually change it yourself with whatever MUA you are comfortable with.
97 Q: I sent a patch and I'm wondering what happened to it.  How can I tell
98    whether it got merged?
125    off to Greg.  If Greg already has the patch, then it will be here:
137 Q: I see a network patch and I think it should be backported to stable.
138    Should I request it via "stable@vger.kernel.org" like the references in
142    if it is already queued.  If not, then send a mail to netdev, listing
143    the upstream commit ID and why you think it should be a stable candidate.
147    explicitly indicate why it is a critical fix and exactly what users are
149    think it has been overlooked, vs. having been considered and rejected.
151    Generally speaking, the longer it has had a chance to "soak" in mainline,
152    the better the odds that it is an OK candidate for stable.  So scrambling
153    to request a commit be added the day after it appears should be avoided.
155 Q: I have created a network patch and I think it should be backported to
159 A: No.  See above answer.  In short, if you think it really belongs in
161    gets impacted by the bugfix and how it manifests itself, and when the
164    stable queue if it really warrants it.
166    If you think there is some valid information relating to it being in
181    it is requested that you make it look like this:
190 A: Make it the latter style, so that eventually all code in the domain of
217    to why it happens, and then if necessary, explain why the fix proposed
220    If it is your first patch, mail it to yourself so you can test apply
221    it to an unpatched tree to confirm infrastructure didn't mangle it.