lkml.org 
[lkml]   [2005]   [Dec]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Date
    From
    Subject[PATCH] Documentation: Update to SubmittingPatches
    from ian McDonald

    Use of git-diff

    Signed-off-by: Ian McDonald <imcdnzl@gmail.com>
    ---
    diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
    index 237d54c..b8d746a 100644
    --- a/Documentation/SubmittingPatches
    +++ b/Documentation/SubmittingPatches
    @@ -20,10 +20,24 @@ SECTION 1 - CREATING AND SENDING YOUR CH



    -1) "diff -up"
    -------------
    +1) Creating a diff file
    +-----------------------

    -Use "diff -up" or "diff -uprN" to create patches.
    +You can use git-diff which makes your life easy. If you want it to be more
    +difficult then carry on reading.
    +
    +Make sure your patch does not include any extra files which do not
    +belong in a patch submission. Make sure to review your patch -after-
    +generated it with diff(1), to ensure accuracy.
    +
    +If your changes produce a lot of deltas, you may want to look into
    +splitting them into individual patches which modify things in
    +logical stages. This will facilitate easier reviewing by other
    +kernel developers, very important if you want your patch accepted.
    +There are a number of scripts which can aid in this:
    +
    +Use "diff -up" or "diff -uprN" to create patches
    +------------------------------------------------

    All changes to the Linux kernel occur in the form of patches, as
    generated by diff(1). When creating your patch, make sure to create it
    @@ -61,16 +75,6 @@ patch. The "dontdiff" file is included
    2.6.12 and later. For earlier kernel versions, you can get it
    from <http://www.xenotime.net/linux/doc/dontdiff>.

    -Make sure your patch does not include any extra files which do not
    -belong in a patch submission. Make sure to review your patch -after-
    -generated it with diff(1), to ensure accuracy.
    -
    -If your changes produce a lot of deltas, you may want to look into
    -splitting them into individual patches which modify things in
    -logical stages. This will facilitate easier reviewing by other
    -kernel developers, very important if you want your patch accepted.
    -There are a number of scripts which can aid in this:
    -
    Quilt:
    http://savannah.nongnu.org/projects/quilt
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/
    \
     
     \ /
      Last update: 2005-12-20 03:34    [W:0.035 / U:120.736 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site