On Wed, Nov 21, 2012 at 06:44:45PM +0100, Jan Kara wrote:
> Hello,
>
> I have a question regarding tagging of patches targetted in -stable
> kernels. We have this 'CC: [email protected] # something' tag. Now
> inconvenient thing is that when I create a patch and have such tag in it,
> then git-send-email will mangle the address because of the #. Now even if
> git-send-email started to ignore the part after #, we don't really want
> [email protected] to get the patch since it is eligible for -stable
> only after it is merged upstream. So the CC form of the tag seems to be
> kind of inconvenient. Won't it be better to have some different tag?
I don't have any particular attachment to this odd format, but I
would like to see *some* format properly standardised. I want to be
able to script:
for each new commit cc'd to stable:
if no version restriction is specified:
add to patch queue(s) pending check for suitability
elif version restriction can be parsed:
add to patch queue(s) or drop based on version comparison
else:
show version restriction and ask whether/where to add it
...with as few questions asked as possible. As yet, though, I haven't
bothered trying to parse the variety of different ways people write
version restrictions, but the script does require them to be preceded
by a '#'.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
