Lines Matching refs:it
40 Q: How often do changes from these trees make it to the mainline Linus tree?
46 merge window is closed, and it is called/tagged ``-rc1``. No new
90 and note the top of the "tags" section. If it is rc1, it is early in
91 the dev cycle. If it was tagged rc7 a week ago, then a release is
105 can manually change it yourself with whatever MUA you are comfortable
108 Q: I sent a patch and I'm wondering what happened to it?
110 Q: How can I tell whether it got merged?
130 it to the maintainer to figure out what is the most recent and current
137 patches such that it is clear this is the latest and greatest set of patches
140 Q: I submitted multiple versions of a patch series and it looks like a version other than the last …
142 A: There is no revert possible, once it is pushed out, it stays like that.
158 to Greg. If Greg already has the patch, then it will be here:
172 Q: I see a network patch and I think it should be backported to stable.
174 Q: Should I request it via stable@vger.kernel.org like the references in
177 to see if it is already queued. If not, then send a mail to netdev,
178 listing the upstream commit ID and why you think it should be a stable
183 still apply. So you need to explicitly indicate why it is a critical
185 convince yourself that you *really* think it has been overlooked,
188 Generally speaking, the longer it has had a chance to "soak" in
189 mainline, the better the odds that it is an OK candidate for stable. So
190 scrambling to request a commit be added the day after it appears should
193 Q: I have created a network patch and I think it should be backported to stable.
197 A: No. See above answer. In short, if you think it really belongs in
199 gets impacted by the bug fix and how it manifests itself, and when the
202 queue if it really warrants it.
204 If you think there is some valid information relating to it being in
228 it is requested that you make it look like this::
237 A: Make it the latter style, so that eventually all code in the domain
261 how any new interface is used and how well it works.
275 └─ [PATCH net-next 2/3] net: some feature do it
280 Posting as one thread is discouraged because it confuses patchwork
289 end-user visible symptom, the underlying reason as to why it happens,
292 mis-indent function arguments that span multiple lines. If it is your
293 first patch, mail it to yourself so you can test apply it to an
294 unpatched tree to confirm infrastructure didn't mangle it.