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

[PATCH v2 0/1] config: add back code comment

From
Kristoffer Haugsbakk <code@khaugsbakk.name>
Date
Jan 29, 2024, 17:57 UTC
Message-ID
<cover.1706550761.git.code@khaugsbakk.name>
In-Reply-To
<48d66e94ece3b763acbe933561d82157c02a5f58.1706466321.git.code@khaugsbakk.name>

This is a follow-up to the kh/maintenance-use-xdg-when-it-should [series] which was merged in 12ee4ed506 (Merge branch 'kh/maintenance-use-xdg-when-it-sho.., 2024-01-26).

I dropped a code comment while iterating on a refactor. It still makes as much sense in this context as before the refactor (it’s a _refactor_ in the sense of “don’t change code behavior”).

The code comment was moved to `config.c` in patch v1 3/4.[1] But review feedback said that this comment didn’t fit in this new place and that we shouldn’t `die()` in `git_global_config`. So in v2 3/4[2] I removed the comment in `git_global_config`. But I forgot to put the comment back to its original place, where it still makes as much sense as before my series.

See the cover letter on the first version for the diff when I squash this patch into c15129b699 (config: factor out global config file retrieval, 2024-01-18).

Sorry about the churn.
Cc: ps@pks.im
§ Changes in v2
Add an ack trailer.

This is the (tentative) final version. I read (interpreted) `SubmittingPatches` as saying that the final version should be sent, even though it’s just to add an additional trailer. I’m open for feedback on the submission process of course.

I’ve added it after my signoff since it seems preferred to maintain the chronology (although in this case either choice seems equally clear). Also it seemed more common in the recent Git log.

🔗 series: https://lore.kernel.org/git/cover.1697660181.git.code@khaugsbakk.name/ 🔗 1: https://lore.kernel.org/git/147c767443c35b3b4a5516bf40557f41bb201078.1697660181.git.code@khaugsbakk.name/ 🔗 2: https://lore.kernel.org/git/32e5ec7d866ff8fd26554b325812c6e19cb65126.1705267839.git.code@khaugsbakk.name/

Kristoffer Haugsbakk (1):
  config: add back code comment
 builtin/config.c | 6 ++++++
 1 file changed, 6 insertions(+)
Range-diff against v1:
1:  48d66e94ec ! 1:  24f536d575 config: add back code comment
    @@ Commit message
         which explains `$HOME not set`.
     
         Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
    +    Acked-by: Patrick Steinhardt <ps@pks.im>
     
      ## builtin/config.c ##
     @@ builtin/config.c: int cmd_config(int argc, const char **argv, const char *prefix)
-- 
2.43.0
Previous: Junio C HamanoNext: Kristoffer Haugsbakk
Message 5 of 6 in “config: add back code comment”
  1. 0/1 config: add back code commentKristoffer Haugsbakk, Jan 28, 2024
  2. 1/1 config: add back code commentKristoffer Haugsbakk, Jan 28, 2024
  3. Patrick SteinhardtJan 29, 2024
  4. Junio C HamanoJan 29, 2024
  5. 0/1 config: add back code commentKristoffer Haugsbakk, Jan 29, 2024
  6. 1/1 config: add back code commentKristoffer Haugsbakk, Jan 29, 2024

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.