diff options
| author | GNU Hurd wiki engine <web-hurd@gnu.org> | 2007-12-19 15:07:36 +0000 |
|---|---|---|
| committer | GNU Hurd wiki engine <web-hurd@gnu.org> | 2007-12-19 15:07:36 +0000 |
| commit | 4cf555959fee67900bbeec33f61f333b93f595fb (patch) | |
| tree | 8c15ff06b4bed7acb11f08648d13ddac5712970d /hurd/running/debian/patch_submission.mdwn | |
| parent | 2ac159d271337ef53b9246401d02d704ff4bb9bd (diff) | |
web commit by MichaelBanck: fix url links
Diffstat (limited to 'hurd/running/debian/patch_submission.mdwn')
| -rw-r--r-- | hurd/running/debian/patch_submission.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/hurd/running/debian/patch_submission.mdwn b/hurd/running/debian/patch_submission.mdwn index 4ae118e1..7f9c8265 100644 --- a/hurd/running/debian/patch_submission.mdwn +++ b/hurd/running/debian/patch_submission.mdwn @@ -10,7 +10,7 @@ If you fixed a Debian package which FTBFS (fails to build from source), you shou If it is not a Debian-specific patch, you should strongly consider submitting the patch upstream for inclusion. This applies even more so if it is a GNU package, or otherwise frequently used package, or you know upstream anyway. -If you had to change the code considerably and are not 100% sure you did not introduce a regression, or are not very experienced with these kinds of code changes, you should first submit your patch for review to the Debian alioth patch tracker at http://alioth.debian.org/tracker/?atid=410472&group_id=30628&func=browse +If you had to change the code considerably and are not 100% sure you did not introduce a regression, or are not very experienced with these kinds of code changes, you should first submit your patch for review to the [Debian alioth patch tracker](http://alioth.debian.org/tracker/?atid=410472&group_id=30628&func=browse). If the patch is trivial, or one of the Debian porters approved your patch for submission, submit the patch to the Debian BTS (bug tracking system). You can either use the reportbug tool, or just simple mail. In any case, you should follow these guidelines: @@ -19,7 +19,7 @@ If the patch is trivial, or one of the Debian porters approved your patch for su * Severity: should be "important" * Add "Tags: patch" -In the bug description, mention that the package fails to build on hurd-i386 and (if possible) quote the failure. If possible, point to the failing build log from http://buildd.debian-ports.org/build.php +In the bug description, mention that the package fails to build on hurd-i386 and (if possible) quote the failure. If possible, point to the failing build log from <http://buildd.debian-ports.org/build.php>. Then, explain the failure (Debian maintainers usually do not know much about Hurd-specific failures), and attach the patch. |