Hi Junio,
On Tue, 23 Dec 2014, Junio C Hamano wrote:
> On Tue, Dec 23, 2014 at 9:28 AM, Johannes Schindelin
> wrote:
> >> Johannes Schindelin writes:
> >>
> >> > And *still*, this is *just* a global table with defaults. I would *still*
> >> > need to copy-on-write when the first customization o
On Tue, Dec 23, 2014 at 9:28 AM, Johannes Schindelin
wrote:
>> Johannes Schindelin writes:
>>
>> > And *still*, this is *just* a global table with defaults. I would *still*
>> > need to copy-on-write when the first customization of the severity level
>> > takes place because I cannot allow the gl
Hi Junio,
On Tue, 23 Dec 2014, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > And *still*, this is *just* a global table with defaults. I would *still*
> > need to copy-on-write when the first customization of the severity level
> > takes place because I cannot allow the global defau
Johannes Schindelin writes:
> And *still*, this is *just* a global table with defaults. I would *still*
> need to copy-on-write when the first customization of the severity level
> takes place because I cannot allow the global defaults to be modified by
> one caller (that would defeat the whole p
Hi Junio,
On Tue, 23 Dec 2014, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > However, if we had to change the lookup such that it uses an array
> > always, we would have to introduce a function to initialize the
> > struct, always, in particular we would have to find a place to call
Johannes Schindelin writes:
> However, if we had to change the lookup such that it uses an array always,
> we would have to introduce a function to initialize the struct, always, in
> particular we would have to find a place to call that initialization
> function in, say, builtin/fsck.c (actually
Hi Junio,
On Mon, 22 Dec 2014, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > For example, try to spot the error here:
> >
> > ...
> > F(ALMOST_HAPPY, INFO) \
> > F(CANNOT_RECOVER, ERROR) \
> > F(COFFEE_IS_EMPTY, WARN) \
> > F(JUST_BEING_CHATTY, INFO) \
> > F(
Johannes Schindelin writes:
> For example, try to spot the error here:
>
> ...
> F(ALMOST_HAPPY, INFO) \
> F(CANNOT_RECOVER, ERROR) \
> F(COFFEE_IS_EMPTY, WARN) \
> F(JUST_BEING_CHATTY, INFO) \
> F(LIFE_IS_GOOD, INFO) \
> F(MISSING_SOMETHING_VITAL, FATAL_
Hi Junio,
On Mon, 22 Dec 2014, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > On Mon, 22 Dec 2014, Junio C Hamano wrote:
> >
> >> Johannes Schindelin writes:
> >>
> >> >> In other words, at some point wouldn't we be better off with
> >> >> something like this
> >> >>
> >> >>
Johannes Schindelin writes:
> Hi Junio,
>
> On Mon, 22 Dec 2014, Junio C Hamano wrote:
>
>> Johannes Schindelin writes:
>>
>> >> In other words, at some point wouldn't we be better off with
>> >> something like this
>> >>
>> >> struct {
>> >> enum id;
>> >> const ch
Hi Junio,
On Mon, 22 Dec 2014, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> >> In other words, at some point wouldn't we be better off with
> >> something like this
> >>
> >>struct {
> >>enum id;
> >> const char *id_string;
> >> enum e
Johannes Schindelin writes:
>> In other words, at some point wouldn't we be better off with
>> something like this
>>
>> struct {
>> enum id;
>> const char *id_string;
>> enum error_level { FSCK_PASS, FSCK_WARN, FSCK_ERROR };
>> } possible_f
Hi Junio,
On Wed, 10 Dec 2014, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > There are legacy repositories out there whose older commits and tags
> > have issues that prevent pushing them when 'receive.fsckObjects' is set.
> > One real-life example is a commit object that has been h
Johannes Schindelin writes:
> There are legacy repositories out there whose older commits and tags
> have issues that prevent pushing them when 'receive.fsckObjects' is set.
> One real-life example is a commit object that has been hand-crafted to
> list two authors.
>
> Often, it is not possible
There are legacy repositories out there whose older commits and tags
have issues that prevent pushing them when 'receive.fsckObjects' is set.
One real-life example is a commit object that has been hand-crafted to
list two authors.
Often, it is not possible to fix those issues without disrupting th
15 matches
Mail list logo
