Per-project patch prefixes
Hi,
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:
1. kernel:
- bluetooth-next -> for patches against Gustavo's bluetooth-next
- bluetooth-current -> for patches against Gustavo's bluetooth-2.6
2. BlueZ:
- bluez
3. obexd:
- obexd
This is just an idea, what do you think?
Cheers,
Signature · 1 line
Vinicius
Quoted 5 lines · Vinicius Costa Gomes
Hi,
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"
You may also want this(if you never configured it :
[sendemail]
to = [email protected]
Quoted 10 lines
1. kernel:
- bluetooth-next -> for patches against Gustavo's bluetooth-next
- bluetooth-current -> for patches against Gustavo's bluetooth-2.62. BlueZ:
- bluez3. obexd:
- obexd
There is hcidump missing here.
Gustavo
Quoted 11 lines · Vinicius Costa Gomes
Hi,
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:
1. kernel:
- bluetooth-next -> for patches against Gustavo's bluetooth-next
- bluetooth-current -> for patches against Gustavo's bluetooth-2.6
Quoted 7 lines
2. BlueZ:
- bluez3. obexd:
- obexdThis is just an idea, what do you think?
Or we could stop playing with mailing-lists and use bugzillas for the non-kernel bits...
Marcel Holtmann
maintainerHi Gustavo,
Quoted 9 lines
Quoted 3 lines
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.
Regards
Marcel
Hi,
Quoted 7 lines · Marcel Holtmann
Quoted 7 lines
Quoted 3 lines
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:
Quoted 6 lines
Quoted 2 lines
[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
Luiz Augusto von Dentz
maintainerHi Marcel,
On Wed, Jun 15, 2011 at 2:10 PM, Marcel Holtmann <[email protected]> wrot= e:
Quoted 3 lines
Hi Gustavo,
Quoted 1 line
Quoted 1 line
Now, this list receives patches for at least 3 different projects, so =
how
Quoted 1 line
Quoted 1 line
Quoted 1 line
about using different subject prefixes for each priject? The first thi=
ng
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
that comes to mind is this:
This is a great idea. It can a lot when identifying patches, and you can=
do
Quoted 8 lines
Quoted 4 lines
this to the project's .git/config:
[format]
=A0 =A0 =A0 =A0 subjectprefix =3D "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
--=20
Luiz Augusto von Dentz
Computer Engineer
Quoted 17 lines · Johan Hedberg
Hi,
Quoted 7 lines · Marcel Holtmann
Quoted 7 lines
Quoted 3 lines
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:
Quoted 6 lines
Quoted 2 lines
[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.
Quoted 6 lines
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.
So no modifications for the kernel patches. "Bluetooth:" prefix is enough to me as well.
Gustavo