Messages in this thread | | | Date | Sun, 18 Aug 2019 11:15:37 +0200 | From | Pavel Machek <> | Subject | stable markup was Re: [PATCH 1/1] Fix: trace sched switch start/stop racy updates |
| |
Hi!
> The most I'll take is two separate patches. One is going to be marked > for stable as it fixes a real bug. The other is more for cosmetic or > theoretical issues, that I will state clearly "NOT FOR STABLE", such > that the autosel doesn't take them.
Do we have standartized way to mark "this is not for stable"? Because I often think "I'd really hate to see this in stable"...
On a related note, it would be nice to have standartized way to marking corresponding upstream commit. (Currently three methods are in use).
Upstream: XXXX
in the signoff area would be nice, clearly marking who touched the patch before mainline and who after.
Best regards,
Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html [unhandled content-type:application/pgp-signature] | |