Re: tig: bug when binding to 'generic'?

From: Taylor Blau <me@ttaylorr.com>
Date: May 4, 2020, 23:14 UTC
Message-ID: <20200504231408.GI45250@syl.local>
In-Reply-To: <xmqqsggfe23v.fsf@gitster.c.googlers.com>

On Mon, May 04, 2020 at 04:01:40PM -0700, Junio C Hamano wrote:

Show 21 quoted lines

> Taylor Blau <me@ttaylorr.com> writes:
>
> > Thanks for clarifying. I was a little confused when I read your patch
> > series, since on first blush I thought that you were submitting it to be
> > applied in Git's integration branches, and not Tig's.
> >
> > In either case, the heads-up is appreciated, but I do not think
> > necessary in general. I am not sure about the feelings of others, but I
> > do not think Tig-specific bugs need to be reported on Git's mailing
> > list.
> >
> > Of course, if there are Git bugs that affect Tig (or any other project),
> > we would be interested in hearing about them.
> >
> > That's all to say that I think the README there should be updated.
>
> FWIW, I do not mind seeing tig related improvements discussed here
> (I am assuming tig does not have its own development list).  That is
> how we've been operating with other "projects around Git", like
> "imerge" and "tbdiff" (no need to look for the latter these days,
> though).

Ah, fair enough: I do remember seeing an imerge query on the list a couple of days (weeks?) ago.

> Unless Jonas and others who are involved find the list traffic here
> is too heavy and messages about tig will be drowned in here, I do
> not see a reason to kick them out.

OK, that sounds good (it wasn't really up to me anyway, but I'm glad that I know how you feel about the matter ;)).

Thanks, Taylor