From: Kaartic Sivaraam Date: Sun, 30 Jul 2017 11:09:21 GMT Subject: [PATCH 2/2] doc: add another way to identify if a patch has been merged Message-ID: <20170730110921.11805-2-kaarticsivaraam91196@gmail.com> In-Reply-To: <20170730110921.11805-1-kaarticsivaraam91196@gmail.com> Signed-off-by: Kaartic Sivaraam --- I'm not sure if the first one (pull --rebase) is still required and hence leaving it as such. Let me know if it could be removed. Documentation/SubmittingPatches | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 9d0dab08d..a800e54a7 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 () you can use + 'git cherry master ' 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