Hi! Some time ago when we were doing the switch to quilt, we'd talked
about renaming the patches to something sensible. I proposed the
following naming scheme, which didn't receive any comments. I'm
proposing it one more time, and will start moving us towards it if I
hear nothing in, say, a week:
## {local|branch|cvs|submitted}-{ARCH|all}-{"Description}"
## Branch means commited in the upstream branch.
## CVS means committed in the upstream trunk.
## Submitted means we're hopeful that it will go in.
## Local means that it's not going upstream.
## The goal is to get all patches to "Branch". Patches should be split
by
## arch so that it's easy to send just the relevant bits to various
## arch maintainers if needed.
I find this scheme useful because I can tell at a glance which patches
are ones that are ours to carry forward, and which ones I need to work
on to get upstream. I can also pretty clearly see how much out of sync
a given arch is from upstream.
and here's a sampling of how the patches look once renamed:
## Branch:
## CVS:
cvs-all-tlscrash
cvs-all-strxfrm
cvs-sparc-datastart
cvs-mash-rlimit-rtprio
## Submitted:
submitted-hppa-drop-utimes
submitted-hppa-configure
submitted-hppa-linuxthreads
submitted-hppa-sysdeps
submitted-hppa-iitlbp
submitted-hppa-fenv-align
submitted-hppa-fpu
## Local:
local-i386-i686biarch
local-sparc-v9biarch
local-all-makeconfig
local-all-ldconfig
local-all-ldd
Although when you're in the situation that RMS is telling you that
you're being too ideological about freedom, maybe, just maybe, it's
true.
- Matthew Wilcox
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=