Hi, On Wed, Jun 15, 2011, Marcel Holtmann wrote: > > > Now, this list receives patches for at least 3 different projects, so how > > > about using different subject prefixes for each priject? The first thing > > > that comes to mind is this: > > > > This is a great idea. It can a lot when identifying patches, and you can do > > this to the project's .git/config: > > > > [format] > > subjectprefix = "bluetooth-next" > > as long as patches come in as [PATCH bluetooth-next v2] or something > similar I am fine with this. I want the [PATCH ...] prefix kept alive > since that is one thing that git did right from the beginning. The mandatory part then becomes "[PATCH bluetooth-next] Bluetooth: ". That doesn't leave much to the really valuable part, especially if you're on a 80-column wide terminal. Add Subject: to the beginning and you've got even less. Kernel patches already have the Bluetooth: prefix in the subject so they are pretty easy to spot IMHO. For obexd OTOH I'd be fine with a [PATCH obexd] convention. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
