On Thu, Aug 26, 2010 at 09:19:23AM -0700, James wrote: > On 08/26/2010 09:15 AM, Kevron Rees wrote: > >This is a patch to meego-handset-dialer. I at least cc'd the maintainer, > >so he should know about it. I wonder if there is a way to do something > >like "[PATCH 1/2 meego-handset-dialer]<subject>" using git-format-patch > >or git-send-email... That would help clear up what the patch is for. > Looks like --subject-prefix might do what you want: > > git format-patch --subject-prefix "PATCH foobar" --numbered ... > > would prefix the patch subject as: > > [PATCH foobar x/y] ... >
Excellent idea. This ought to go in the contribution-guidelines[1] or at least get discussed/proposed on the wiki page for the same subject[2]. Oh it seems that wiki page is not longer open for comments... Dawn, maybe we could use that wiki page for continuing discussion on this? Which brings us back to the subject of "project" naming and it's use in the patch subject header that I complianed about in a seperate thread. I will take that back to the original thread and not hijack this one, but I will mention that I believe some of our project names are just too artificially long to make this practical w/out coming up with "short" versions of their names, or a standard abbreviation mapping. Shane... [1]http://meego.com/about/contribution-guidelines [2]http://wiki.meego.com/Contributing_code_to_MeeGo _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
