[PATCH 2/2] doc: add another way to identify if a patch has been merged

From

Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>

Date

Aug 1, 2017, 16:05 UTC

Message-ID

<20170801160539.5587-2-kaarticsivaraam91196@gmail.com>

In-Reply-To

<20170801160539.5587-1-kaarticsivaraam91196@gmail.com>

Signed-off-by: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
---
 Documentation/SubmittingPatches | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 886fe3650..7197709ee 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -386,6 +386,10 @@ Know the status of your patch after submission
   tell you if your patch is merged in pu if you rebase on top of
   master).
 
+* If you made your change in a separate branch (<branch>) you can use
+  "git cherry master <branch>" to see if the change has been merged
+  into master.
+
 * Read the Git mailing list, the maintainer regularly posts messages
   entitled "What's cooking in git.git" and "What's in git.git" giving
   the status of various proposed changes.

-- 
2.14.0.rc1.434.g6eded367a