On Fri, Jul 12, 2013 at 03:53:17PM -0400, Steven Rostedt wrote: > On Fri, 2013-07-12 at 12:44 -0700, Linus Torvalds wrote: > > > They can be useful for "local" notes (they can be very powerful for > > certain workflows), but they won't be pulled and pushed by me. > > Perhaps notes can be used as that reminder to send to stable. Tag a > commit with a note, and have some automated process that monitors > Linus's tree and when a commit makes it in, automate an email to stable > with said commit. Ick, no, I'm not going to be using git notes for anything, sorry. Is it _really_ all that hard to remember what to mark for stable inclusion? If you figure it out after you have committed the patch, then just put a copy of it somewhere to remind yourself. That seems to be what both David and I do with no problems, and I think we both deal with more individual patches and developers than probably most everyone else combined. That's what mailboxes are for, use a script of 'git send-email' to send it to yourself and save it somewhere. Use patchwork. Use a text file to remind yourself. Use quilt, like Andrew does, he has a great track record of marking patches for the stable trees properly. Use something, it really isn't that hard, or at least, it sure shouldn't be, if you really care about it. greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html