On Wed, 2017-07-05 at 12:19 -0700, Junio C Hamano wrote:
> I honestly do not see your point. Yes, I said that the change
> indicates that there is no useful example found (so far). That does
> not necessarily mean that we must find a useful example so that we
> can keep this sample script, which
Kaartic Sivaraam writes:
>> On Wed, 2017-07-05 at 10:00 -0700, Junio C Hamano wrote:
>> > I am not so sure that we are searching for them, to be honest (who
>> > are we in this context anyway?)
>>
> Imagining HTML could be used in plain-text,
>
> I think I misinterpreted your sentence in one of
> On Wed, 2017-07-05 at 10:00 -0700, Junio C Hamano wrote:
> > I am not so sure that we are searching for them, to be honest (who
> > are we in this context anyway?)
>
Imagining HTML could be used in plain-text,
I think I misinterpreted your sentence in one of the other
mails (found below), Sor
On Wed, 2017-07-05 at 10:00 -0700, Junio C Hamano wrote:
> Kaartic Sivaraam writes:
>
> > So, we're searching for scripts that
> > could both be helpful to users and could serve as a good sample to
> > prove what could be done using the hooks.
>
> I am not so sure that we are searching for them
Kaartic Sivaraam writes:
> So, we're searching for scripts that
> could both be helpful to users and could serve as a good sample to
> prove what could be done using the hooks.
I am not so sure that we are searching for them, to be honest (who
are we in this context anyway?)
This sounds like
Hello all,
There's an attempt in progress to replace the part of the sample
"prepare-commit-msg" hook that comments the "Conflicts" part of a merge
commit message. This is being done as the "Conflicts" portion is
commented by default for quite some time (since 2014) and thus the
script in the hook
6 matches
Mail list logo
