[PATCH v2 0/1] builtin/blame.c: bit field constants into bit shift format

2019-10-17 Thread Hariom Verma via GitGitGadget
we are looking at bitfield constants, and elsewhere in the Git source code, such cases are handled via bit shift operators rather than octal numbers, which also makes it easier to spot holes in the range (if, say, 1<<5 was missing, it is easier to spot it between 1<<4 and 1<<6 than it is to spot a

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

2019-10-17 Thread Hariom Verma via GitGitGadget
From: Hariom Verma We are looking at bitfield constants, and elsewhere in the Git source code, such cases are handled via bit shift operators rather than octal numbers, which also makes it easier to spot holes in the range (if, say, 1<<5 was missing, it is easier to spot it between 1<<4 and 1<<6

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

2019-10-16 Thread Hariom Verma via GitGitGadget
we are looking at bitfield constants, and elsewhere in the Git source code, such cases are handled via bit shift operators rather than octal numbers, which also makes it easier to spot holes in the range (if, say, 1<<5 was missing, it is easier to spot it between 1<<4 and 1<<6 than it is to spot a

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

2019-10-16 Thread Hariom Verma via GitGitGadget
From: Hariom Verma We are looking at bitfield constants, and elsewhere in the Git source code, such cases are handled via bit shift operators rather than octal numbers, which also makes it easier to spot holes in the range (if, say, 1<<5 was missing, it is easier to spot it between 1<<4 and 1<<6