[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]]

[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]


Patch Life Cycle
================

[[!toc startlevel=2]]


* * *


Start
-----

Follow the steps listed on the [[package porting page|porting_guide_for_dummies]].


Discuss
-------

Send the patch for review to [debian-hurd@lists.debian.org](mailto:debian-hurd@lists.debian.org).  
**Before** sending the patch, make sure that you've solved all the known problems listed in the [[package porting general introduction|hurd/porting/guidelines]] 
and the [[porting guide for dummies|porting_guide_for_dummies]].


Submit Draft
------------

When the patch is good enough, you can write the draft of the official bug report.  
This draft should first be sent for review to [debian-hurd@lists.debian.org](mailto:debian-hurd@lists.debian.org) with the patch attached.

Here is an example for memstat:

    Source: memstat
    Version: 0.9
    Severity: important
    Tags: patch
    User: debian-hurd@lists.debian.org
    Usertags: hurd
    X-DebBugs-CC: debian-hurd@lists.debian.org

    Hi,

    This patch solves the build problems for GNU/Hurd due to PATH_MAX
    issues. The solution is to make dynamic string allocations instead of
    using fixed length buffers. The patch involves one file, and is
    trivial. Parts of the the code has been reviewed by GNU/Hurd developers
    and Debian GNU/Hurd developers and maintainers.

    FIXME:
    Is it really useful to check if BUFSIZ is defined?

    TODO:
    Should the "whole package" be tested with valgrind on GNU/Linux?!
    If yes, is there a standard procedure to do it?!

    Thanks! 
    Special thanks to Jérémie and Richard for their comments!

    (Not submitted yet, comments are welcome.)

Once it's been approved, you can proceed to the submission.


Submit
------

The bug report is the same as above, with all the **FIXME**, **TODO** and final comment removed.  
Attach the patch and send it to [submit@bugs.debian.org](mailto:submit@bugs.debian.org).  
Convention for the attachment name is: `fix_FTBFS4Hurd.patch`


Accept
------

Once the patch has been accepted, update your patch page!  
**Congratulations!**