{"thread":{"id":"22064","subject":"[PATCH] SubmittingPatches: hints to know the status of a submitted patch.","startedAt":"2009-12-30T14:51:22Z","lastAt":"2009-12-30T14:51:22Z","messageCount":1,"participants":["Matthieu Moy"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"130560","messageId":"1262184682-9440-1-git-send-email-Matthieu.Moy@imag.fr","threadId":"22064","inReplyTo":null,"subject":"[PATCH] SubmittingPatches: hints to know the status of a submitted patch.","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2009-12-30T14:51:22Z","receivedAt":"2009-12-30T14:51:22Z","isPatch":true,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"\"What happened to my patch\" is pretty much a FAQ on the Git mailing list,\nit deserves a few paragraphs in SubmittingPatches...\n\nSigned-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>\n---\n\n(I had already sent this patch as a draft RFC, admitedly rather well\nhidden within another thread. Let's retry a bit more explicitly ;-) )\n\n Documentation/SubmittingPatches |   14 ++++++++++++++\n 1 files changed, 14 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches\nindex 76fc84d..c686f86 100644\n--- a/Documentation/SubmittingPatches\n+++ b/Documentation/SubmittingPatches\n@@ -280,6 +280,20 @@ people play with it without having to pick up and apply the patch to\n their trees themselves.\n \n ------------------------------------------------\n+Know the status of your patch after submission\n+\n+* You can use Git itself to find out when your patch is merged in\n+  master. 'git pull --rebase' will automatically skip already-applied\n+  patches, and will let you know. This works only if you rebase on top\n+  of the branch in which your patch has been merged (i.e. it will not\n+  tell you if your patch is merged in pu if you rebase on top of\n+  master).\n+\n+* Read the git mailing list, the maintainer regularly posts messages\n+  entitled \"What's cooking in git.git\" and \"What's in git.git\" giving\n+  the status of various proposed changes.\n+\n+------------------------------------------------\n MUA specific hints\n \n Some of patches I receive or pick up from the list share common\n-- \n1.6.6.71.gcc720.dirty\n"}]}