Re: Per-project patch prefixes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Marcel,

On Wed, Jun 15, 2011 at 2:10 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote:
> Hi Gustavo,
>
>> > 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.

So an obexd patch would look like this:

[PATCH obexd 1/4] Add initial support for OBEX Action command

-- 
Luiz Augusto von Dentz
Computer Engineer
--
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


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux