Re: [PATCH v2 03/10] commit: add generation number to struct commmit

Derrick Stolee writes: > How about we do a slightly different > arrangement for these overflow commits? > > Instead of storing the commits in the commit-graph file as "0" (which > currently means "written by a version of git that did not compute > generation numbers") we could

Re: [PATCH v2 03/10] commit: add generation number to struct commmit

On 4/10/2018 10:31 PM, Junio C Hamano wrote: Derrick Stolee writes: The generation number of a commit is defined recursively as follows: * If a commit A has no parents, then the generation number of A is one. * If a commit A has parents, then the generation number of A

Re: [PATCH v2 03/10] commit: add generation number to struct commmit

Derrick Stolee writes: > The generation number of a commit is defined recursively as follows: > > * If a commit A has no parents, then the generation number of A is one. > * If a commit A has parents, then the generation number of A is one > more than the maximum

Re: [PATCH v2 03/10] commit: add generation number to struct commmit

On Mon, Apr 9, 2018 at 9:42 AM, Derrick Stolee wrote: > The generation number of a commit is defined recursively as follows: > > * If a commit A has no parents, then the generation number of A is one. > * If a commit A has parents, then the generation number of A is one >

[PATCH v2 03/10] commit: add generation number to struct commmit

The generation number of a commit is defined recursively as follows: * If a commit A has no parents, then the generation number of A is one. * If a commit A has parents, then the generation number of A is one more than the maximum generation number among the parents of A. Add a uint32_t