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

Re: [PATCH 1/1] builtin/blame.c: constants into bit shift format

From
JTJonathan Tan <jonathantanmy@google.com>
Date
Oct 16, 2019, 19:37 UTC
Message-ID
<20191016193750.258148-1-jonathantanmy@google.com>
In-Reply-To
<20191016191012.ij3zbexu7pxupdho@yadavpratyush.com>
Show 9 quoted lines
> There was some discussion recently about converting these related 
> #defines to enums [0]. We might consider doing that here.
> 
> If you read through that entire thread, you'd see that there were some 
> disagreements about whether using enums for sets of bits is a good idea 
> ([1] and [2]), but it is at least something worth considering while we 
> are on this topic.
> 
> FWIW, I think it is a good idea to use an enum here.
[snip]
> [0] https://public-inbox.org/git/20191010115230.10623-1-wambui.karugax@gmail.com/
> [1] https://public-inbox.org/git/20191014182754.82302-1-jonathantanmy@google.com/
> [2] https://public-inbox.org/git/xmqqk19ag60g.fsf@gitster-ct.c.googlers.com/

Thanks for the handy references. You know my opinion on bitflags as enums from reading them, but I think that we have already had that discussion and came to a conclusion. So don't use an enum here.

The patch itself looks good, and I also prefer the bit shift format over octal.

Previous: Pratyush YadavNext: Pratyush Yadav
Message 4 of 9 in “builtin/blame.c: bit field constants into bit shift format”
  1. 0/1 builtin/blame.c: bit field constants into bit shift formatHariom Verma via GitGitGadget, Oct 16, 2019
  2. 1/1 builtin/blame.c: constants into bit shift formatHariom Verma via GitGitGadget, Oct 16, 2019
  3. Pratyush YadavOct 16, 2019
  4. Jonathan TanOct 16, 2019
  5. Pratyush YadavOct 16, 2019
  6. Junio C HamanoOct 17, 2019
  7. Junio C HamanoOct 17, 2019
  8. 0/1 builtin/blame.c: bit field constants into bit shift formatHariom Verma via GitGitGadget, Oct 17, 2019
  9. 1/1 builtin/blame.c: constants into bit shift formatHariom Verma via GitGitGadget, Oct 17, 2019

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.