summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: b0b3a24)
raw | patch | inline | side by side (parent: b0b3a24)
author | Matthieu Moy <Matthieu.Moy@imag.fr> | |
Wed, 30 Dec 2009 14:51:22 +0000 (15:51 +0100) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Thu, 31 Dec 2009 22:46:08 +0000 (14:46 -0800) |
"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>
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>
Documentation/SubmittingPatches | patch | blob | history |
index 76fc84d8780762e083cd4ca584b9d783b8c0cd81..c686f8646b465860c8a096241797709366cc4dc1 100644 (file)
people play with it without having to pick up and apply the patch to
their trees themselves.
people play with it without having to pick up and apply the patch to
their trees themselves.
+------------------------------------------------
+Know the status of your patch after submission
+
+* You can use Git itself to find out when your patch is merged in
+ master. 'git pull --rebase' will automatically skip already-applied
+ patches, and will let you know. This works only if you rebase on top
+ of the branch in which your patch has been merged (i.e. it will not
+ tell you if your patch is merged in pu if you rebase on top of
+ 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.
+
------------------------------------------------
MUA specific hints
------------------------------------------------
MUA specific hints