From: Dylan Carlson <absinthe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Patch filename conventions (WAS: Proposal: patches.gentoo.org)
Date: Thu, 14 Oct 2004 18:08:05 -0400 [thread overview]
Message-ID: <200410141808.05200.absinthe@gentoo.org> (raw)
In-Reply-To: <200410141638.22597.absinthe@gentoo.org>
On Thu October 14 2004 16:38, Dylan Carlson wrote:
> I'd also like to see a naming convention of patches established.
I know it's bad form to reply to your own message, but I'm doing it anyway.
Here's my quick stab on filename convention:
${PN}-${PV}-arch/use-##-short_desc[-gentoo].diff.bz2
where...
## = the patch number (two digit w/leading zeros) in order added
arch = "any", or arch it applies to
short_desc = ~20 characters or less, use flag at the beginning (if applic),
underscores between words
[-gentoo] = optional, if diff is gentoo-specific and/or originated @ gentoo
examples:
glibc-2.3.4-any-01-pax_localedef_fix_trampoline.diff.bz2
glibc-2.3.4-any-02-pax_pt.diff.bz2
glibc-2.3.4-any-03-pax_i386_got_fix.bz2
glibc-2.3.4-amd64-01-conf_libdir-gentoo.diff.bz2
glibc-2.3.4-mips-01-addabi.diff.bz2
glibc-2.3.4-mips-02-syscall.h.diff.bz2
glibc-2.3.4-mips-03-sysify.diff.bz2
glibc-2.3.4-mips-04-multilib_nolib3264.diff.bz2
glibc-2.3.4-mips-05-pax_dl_execstack_support.diff.bz2
This convention doesn't address files that aren't patches (i.e., conf
files, makefiles, etc)
--
Dylan Carlson [absinthe@gentoo.org]
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-14 22:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 19:09 [gentoo-dev] Proposal: patches.gentoo.org Chris Gianelloni
2004-10-12 19:12 ` Ciaran McCreesh
2004-10-12 19:32 ` George Shapovalov
2004-10-12 19:33 ` Ciaran McCreesh
2004-10-13 12:53 ` Kurt Lieber
2004-10-13 13:28 ` Doug Goldstein
2004-10-12 19:27 ` Marius Mauch
2004-10-12 19:52 ` Beber
2004-10-12 20:11 ` Marius Mauch
2004-10-12 20:10 ` Nicholas Jones
2004-10-12 20:50 ` Jeffrey Forman
2004-10-12 20:57 ` Jeffrey Forman
2004-10-12 23:20 ` Chris Gianelloni
2004-10-13 12:43 ` Kurt Lieber
2004-10-13 9:46 ` Paul de Vrieze
2004-10-13 12:19 ` Lance Albertson
2004-10-13 12:39 ` Kurt Lieber
2004-10-12 19:57 ` Nick Dimiduk
2004-10-12 19:57 ` Ciaran McCreesh
2004-10-12 20:17 ` Chris Gianelloni
2004-10-12 22:04 ` Mike Frysinger
2004-10-13 13:05 ` Kurt Lieber
2004-10-13 15:16 ` Ciaran McCreesh
2004-10-14 12:07 ` Kurt Lieber
2004-10-15 15:13 ` Xavier Neys
2004-10-14 20:38 ` Dylan Carlson
2004-10-14 21:05 ` Mark Loeser
2004-10-15 1:00 ` Chris Gianelloni
2004-10-14 22:08 ` Dylan Carlson [this message]
2004-10-14 22:14 ` [gentoo-dev] Patch filename conventions (WAS: Proposal: patches.gentoo.org) Mike Frysinger
2004-10-15 2:20 ` Dylan Carlson
2004-10-15 2:58 ` Donnie Berkholz
2004-10-15 4:24 ` Dylan Carlson
2004-10-15 5:13 ` Donnie Berkholz
2004-10-15 6:01 ` Dylan Carlson
2004-10-15 6:04 ` Robin H. Johnson
2004-10-15 12:16 ` Kurt Lieber
2004-10-15 0:49 ` [gentoo-dev] Proposal: patches.gentoo.org Chris Gianelloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200410141808.05200.absinthe@gentoo.org \
--to=absinthe@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox