SubmittingPatches: hints to know the status of a submitted patch.
"What happened to my patch" is pretty much a FAQ on the Git mailing list, it deserves a few paragraphs in SubmittingPatches... Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Matthieu Moy committed
Dec 30, 2009 at 15:51 UTC
63cb8215997fa7bef4319339060869a8c9cee8aa
1 file changed
+14
Documentation/SubmittingPatches
+14
@@ -279,6 +279,20 @@ from the list and queue it to 'pu', in order to make it easier for
279
people play with it without having to pick up and apply the patch to
280
their trees themselves.
281
282
+------------------------------------------------
283
+Know the status of your patch after submission
284
+
285
+* You can use Git itself to find out when your patch is merged in
286
+ master. 'git pull --rebase' will automatically skip already-applied
287
+ patches, and will let you know. This works only if you rebase on top
288
+ of the branch in which your patch has been merged (i.e. it will not
289
+ tell you if your patch is merged in pu if you rebase on top of
290
+ master).
291
+
292
+* Read the git mailing list, the maintainer regularly posts messages
293
+ entitled "What's cooking in git.git" and "What's in git.git" giving
294
+ the status of various proposed changes.
295
+
296
------------------------------------------------
297
MUA specific hints
298