Re: [RFC] Kernel naming convention in the merge phase
- Date: Mon, 12 May 2008 13:13:03 -0700
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
- Subject: Re: [RFC] Kernel naming convention in the merge phase
Oliver Hartkopp wrote:
This is no real detail. How can -rc0 break a naming scheme for a robot, when -rc1 doesn't?
Because of things like: - regexp patterns like -(rc|pre)([1-9][0-9]*) - using zero to mean "no rc/pre" - assuming 1 is the immediate decendent of the previous one So on, etc, yadda yadda... -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [RFC] Kernel naming convention in the merge phase
- From: Oliver Hartkopp
- Re: [RFC] Kernel naming convention in the merge phase
- From: H. Peter Anvin
- Re: [RFC] Kernel naming convention in the merge phase
- From: Oliver Hartkopp
- Re: [RFC] Kernel naming convention in the merge phase
- From: H. Peter Anvin
- Re: [RFC] Kernel naming convention in the merge phase
- From: Romano Giannetti
- Re: [RFC] Kernel naming convention in the merge phase
- From: Oliver Hartkopp
- Re: [RFC] Kernel naming convention in the merge phase
- From: H. Peter Anvin
- Re: [RFC] Kernel naming convention in the merge phase
- From: Oliver Hartkopp
- Re: [RFC] Kernel naming convention in the merge phase
- From: H. Peter Anvin
- Re: [RFC] Kernel naming convention in the merge phase
- From: Oliver Hartkopp
- [RFC] Kernel naming convention in the merge phase
- Prev by Date: Re: [PATCH] riscom8: remove redundant null pointer test
- Next by Date: Re: [patch, 2.6.26-rc2] dvb: drivers/media/dvb/ttpci/fdump firmware build error fix
- Previous by thread: Re: [RFC] Kernel naming convention in the merge phase
- Next by thread: Re: [RFC] Kernel naming convention in the merge phase
- Index(es):