diff options
author | Robert Schwebel <r.schwebel@pengutronix.de> | 2011-10-31 20:22:59 +0100 |
---|---|---|
committer | Robert Schwebel <r.schwebel@pengutronix.de> | 2011-10-31 20:22:59 +0100 |
commit | 0ddb658ec5277960b6b525cf7f43765679e2c381 (patch) | |
tree | 7211a02c9a9d3d90440e5564d3f582de60ffcf9f | |
parent | a83fd1517dac1811a1b768868e7ae81df8291975 (diff) | |
download | send-patches-org-0ddb658ec5277960b6b525cf7f43765679e2c381.tar.gz send-patches-org-0ddb658ec5277960b6b525cf7f43765679e2c381.tar.xz |
readme: more updates
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
-rw-r--r-- | README | 43 |
1 files changed, 22 insertions, 21 deletions
@@ -97,9 +97,9 @@ Used-in: <buildsystem> where <buildsystem> can be one of the following (in alphabetical order): - buildroot - crosstool-ng - ptxdist + Buildroot (http://www.buildroot.net) + Crosstool-NG (http://crosstool-ng.org) + PTXdist (http://www.ptxdist.org) The Used-in: tag must only be given by one of the maintainers of the buildsystems in question. Anyone who has write access to the @@ -124,8 +124,6 @@ Send-patches-org: <url> with <url> pointing to the gitweb location of the latest version of this patch. -FIXME: it might be possible to use commit-hooks to autogenerate this - Patch Names ----------- @@ -149,17 +147,10 @@ Upstream Status The upstream status of a patch is documented with these tags: -FIXME - check names from Debian/oe-core - -Upstream-sent-by: Joe Hacker <joe.hacker@send-patches.org>, 2011-10-29 -Upstream-accepted: <URL> -Upstream-rejected: <URL> -Not-for-upstream: <reason> - -/FIXME - -These tags shall be added below the triple-dash line (---), so they are -not sent to the upstream maintainers when posting patches. +Upstream-status: <pending, accepted, rejected> +Upstream-origin: <URL> +Upstream-comment: <comment> +Not-for-upstream: <comment> The Not-for-upstream: tag shall only be given if either upstream is dead or the problem is really a local hack where no proper fix is available. @@ -178,8 +169,6 @@ extraction naming scheme, for example: If the upstream tarball extracts only to a directory named after the package name, the version shall be added with a dash. -FIXME rsc: this probably needs to be formalized more deeply - Below the package directory, each involved build system may have it's own subdirectory, for example: @@ -204,12 +193,24 @@ These rules allow the following workflow: Used-in: tags and use their <buildsystem>/ subdirectory. +autogen.sh Scripts +------------------ + +A package directory may contain a script called autogen.sh. If this +script is there, it is being run by the build system after the patch +series has been applied and before the "configure" stage runs. This +mechanism can for example be used to run the autotools. + + Open Issues ----------- -- What happens with tags if a patch is modified? - Strategy for stable vs. development -- Discuss autogen.sh method +- It might be possible to autogenerate the Send-patches-org: URL by + using commit-hooks. +- The package directory naming scheme probably needs to be formalized + more deeply -[1] FIXME: reference to kernel's canonical patch format +[1] http://lxr.linux.no/#linux+v3.1/Documentation/SubmittingPatches#L472 [2] there are broken quilt versions which cannot cope with empty lines + |