[PATCH 2/2] doc: add another way to identify if a patch has been merged
From: Kaartic Sivaraam <hidden>
Date: 2017-07-30 11:09:08
Subsystem:
documentation, the rest · Maintainers:
Jonathan Corbet, Linus Torvalds
Signed-off-by: Kaartic Sivaraam <redacted> --- 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 (<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