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

[PATCH v2 1/2] SubmittingPatches: replace numbered attributes with names

From
Thomas Gummerer <t.gummerer@gmail.com>
Date
May 30, 2018, 20:52 UTC
Message-ID
<20180530205255.13090-1-t.gummerer@gmail.com>
In-Reply-To
<20180527140433.32277-1-t.gummerer@gmail.com>

Use names instead of numbers for the AsciiDoc attributes that are used for the footnotes. We will add more footnotes in subsequent commits, and attributes should ideally all be unique. Having named attributes will help ensure uniqueness, and we won't have to re-number the attributes if we add a footnote earlier in the document.

In addition it also clarifies that the attribute name/number is not related to the number the footnote will get in the output.

Signed-off-by: Thomas Gummerer <t.gummerer@gmail.com>
---

Thanks Junio, Jonathan and brian for the comments on the previous round at <20180527140433.32277-1-t.gummerer@gmail.com>. This round squashes the two patches I sent previously adding the mentions of the security mailing list into one, and adds this preparatory patch.

The security mailing list is now mentioned twice in SubmittingPatches, to make sure people don't miss it, and the wording was adjusted to match the document better.

 Documentation/SubmittingPatches | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 945f8edb46..27553128f5 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -264,12 +264,12 @@ people who are involved in the area you are touching (the `git
 contacts` command in `contrib/contacts/` can help to
 identify them), to solicit comments and reviews.
 
-:1: footnote:[The current maintainer: gitster@pobox.com]
-:2: footnote:[The mailing list: git@vger.kernel.org]
+:current-maintainer: footnote:[The current maintainer: gitster@pobox.com]
+:git-ml: footnote:[The mailing list: git@vger.kernel.org]
 
 After the list reached a consensus that it is a good idea to apply the
-patch, re-send it with "To:" set to the maintainer{1} and "cc:" the
-list{2} for inclusion.
+patch, re-send it with "To:" set to the maintainer{current-maintainer} and "cc:" the
+list{git-ml} for inclusion.
 
 Do not forget to add trailers such as `Acked-by:`, `Reviewed-by:` and
 `Tested-by:` lines as necessary to credit people who helped your
-- 
2.17.0.1181.g093e983b0
Previous: brian m. carlsonNext: Thomas Gummerer
Message 8 of 11 in “README: note git-security@googlegroups.com”
  1. README: note git-security@googlegroups.comThomas Gummerer, May 27, 2018
  2. Jonathan NiederMay 27, 2018
  3. 2/1 SubmittingPatches: not git-security@googlegroups.comThomas Gummerer, May 27, 2018
  4. Junio C HamanoMay 28, 2018
  5. Thomas GummererMay 29, 2018
  6. Thomas GummererMay 29, 2018
  7. brian m. carlsonMay 29, 2018
  8. 1/2 SubmittingPatches: replace numbered attributes with namesThomas Gummerer, May 30, 2018
  9. 2/2 note git-security@googlegroups.com in more placesThomas Gummerer, May 30, 2018
  10. brian m. carlsonMay 30, 2018
  11. Thomas GummererMay 31, 2018

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.