From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 3 Oct 2016 22:25:18 +0000 (-0700)
Subject: Meta/MaintNotes: hint at 'jch' branch
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3a2f03cfe02c3eb73780d99c3f4378a683369313;p=thirdparty%2Fgit.git

Meta/MaintNotes: hint at 'jch' branch
---

diff --git a/MaintNotes b/MaintNotes
index 2fb965db8c..3cb97cbc9e 100644
--- a/MaintNotes
+++ b/MaintNotes
@@ -196,6 +196,10 @@ in "pu" proves to be in a testable shape, it is merged to "next".
 You can run "git log --first-parent master..pu" to see what topics are
 currently in flight.  Sometimes, an idea that looked promising turns out
 to be not so good and the topic can be dropped from "pu" in such a case.
+The output of the above "git log" talks about a "jch" branch, which is an
+early part of the "pu" branch; that branch contains all topics that
+are in "next" and a bit more (but not all of "pu") and is used by the
+maintainer for his daily work.
 
 The two branches "master" and "maint" are never rewound, and "next"
 usually will not be either.  After a feature release is made from