I've tolerated patches in attachments, but please do not do
this:
This is a multi-part message in MIME format.
--------------010006030902030700040300
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
--------------010006030902030700040300
Content-Type: text/plain;
name="0001-Add-config-example-with-respect-to-branch.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="0001-Add-config-example-with-respect-to-branch.txt"
From: Aneesh Kumar K.V <aneesh.kumar@xxxxxxxxx>
Update config.txt with example with respect to branch
config variable. This give a better idea regarding
how branch names are expected.
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@xxxxxxxxx>
---
Documentation/config.txt | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
Instead have the proposed commit log message (and From: line if
you are forwarding somebody else's patch, or if your MUA does
not record your own name correctly) in the first part (which is
empty in your message).
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html