Skip to contentSkip to conversation

Add config example with respect to branch

PATCH In review Aneesh Kumar K.V 2 participants 2 messages Aug 11, 2016 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Add config example with respect to branch

From: Aneesh Kumar K.V <[email protected]>

Update config.txt with example with respect to branch config variable. This give a better idea regarding how branch names are expected.

---
 Documentation/config.txt |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)
Documentation/config.txt +5 -0
index 9090762..d3518d1 100644
@@ -31,6 +31,11 @@ Example
 		external = "/usr/local/bin/gnu-diff -u"
 		renames = true
 
+	[branch "devel"]
+		remote = origin
+		merge = refs/heads/devel
+
+
 Variables
 ~~~~~~~~~
 
Signature · 1 line
1.4.4.1.g278f-dirty
#1 lore raw

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 <[email protected]>

Update config.txt with example with respect to branch config variable. This give a better idea regarding how branch names are expected.

---
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).