Frank Li <lznuaa@xxxxxxxxx> writes: >> Okay, I will wait for Frank's updates (just fetched tgit.git and it still >> contains the old branch), merge the early part and add the compiler flags. >> > Today, I just update 5 patch according review feedback. > Do I need send it again? Yes, this is the use here. Preferably edit the message to replace [PATCH] with [PATCH v2] or so. > How do I know if patch has been applied main line? Answering the question with another: shouldn't we add a section like this to SubmittingPatches ? >From 3ee45ab5992fd084c130460f07454061ce3cf057 Mon Sep 17 00:00:00 2001 From: Matthieu Moy <Matthieu.Moy@xxxxxxx> Date: Tue, 18 Aug 2009 18:48:47 +0200 Subject: [PATCH] SubmittingPatches: draft section to know patches status Signed-off-by: Matthieu Moy <Matthieu.Moy@xxxxxxx> --- Documentation/SubmittingPatches | 14 ++++++++++++++ 1 files changed, 14 insertions(+), 0 deletions(-) diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 76fc84d..c686f86 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 -- 1.6.4.313.g38b9 -- Matthieu -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html