X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=patchformatting.mdwn;h=cf5bf813c082337c0e3f2799b3f12f1588ef184a;hb=889266d3dfcd3f478978cf136a94f3448696999a;hp=6ff103a2421df3010240c1d492024c66cb884fcc;hpb=8c4b5bfb536e83cfa7958759eeb6d375d5a06185;p=notmuch-wiki

diff --git a/patchformatting.mdwn b/patchformatting.mdwn
index 6ff103a..cf5bf81 100644
--- a/patchformatting.mdwn
+++ b/patchformatting.mdwn
@@ -10,7 +10,7 @@ you should check the following:
 
 2. Read mailing list (archives) and follow the discussions on the patches sent.
 
-3. Get familiar with coding conventions used (in any particular project).
+3. Get familiar with coding conventions used.
 
 This way you get some insight of the look and feel of the patches sent,
 both the way code should be written, how to write commit log messages
@@ -119,6 +119,10 @@ actual patch sending to the mailing list.
 
 ### Sending one patch using compatible (emacs) email client.
 
+Sometimes using git-send-email is not possible; It is not installed by
+default and you don't have privileges to install it or you are not
+able to compile it as it has more build-time requirements as git itself.
+
 One alternative way to send your patches is to use, for example, the
 emacs mail client you've already used to send mails to mailing list.
 In this case you have to be very careful to keep the patch contents