diff options
| author |  Matthieu Moy <Matthieu.Moy@imag.fr> | 2009-12-30 15:51:22 +0100 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2009-12-31 14:46:08 -0800 |
| commit | 63cb8215997fa7bef4319339060869a8c9cee8aa (patch) | |
| tree | 906ad7f1be52e1d895b68cbc00e882e241287a4c | |
| parent | Merge branch 'maint-1.6.1' into maint (diff) | |
| download | tgif-63cb8215997fa7bef4319339060869a8c9cee8aa.tar.xz | |
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>
| -rw-r--r-- | Documentation/SubmittingPatches | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 76fc84d878..c686f8646b 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -280,6 +280,20 @@ 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 Some of patches I receive or pick up from the list share common |