git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] SubmittingPatches : WIP tag in patches

From
PBPranit Bauva <pranit.bauva@zoho.com>
Date
Feb 26, 2016, 14:05 UTC
Message-ID
<56D05BA2.1090502@zoho.com>
---
 Documentation/SubmittingPatches | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/SubmittingPatches
b/Documentation/SubmittingPatches
index 98fc4cc..b2c7664 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -168,7 +168,9 @@ the closing bracket to mark the nature of the patch
is also
 encouraged.  E.g. [PATCH/RFC] is often used when the patch is
 not ready to be applied but it is for discussion, [PATCH v2],
 [PATCH v3] etc. are often seen when you are sending an update to
-what you have previously sent.
+what you have previously sent. [PATCH/WIP] is often used when some
+work is yet left to be done on the patch but you want to get the
+review on the completed part of the patch.

 "git format-patch" command follows the best current practice to
 format the body of an e-mail message.  At the beginning of the
-- 
2.1.4
Next: Eric Sunshine
Message 1 of 5 in “SubmittingPatches : WIP tag in patches”
  1. SubmittingPatches : WIP tag in patchesPranit Bauva, Feb 26, 2016
  2. Eric SunshineFeb 26, 2016
  3. Pranit BauvaFeb 26, 2016
  4. Eric SunshineFeb 26, 2016
  5. Stefan TatschnerFeb 26, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.