git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
May 4, 2020, 23:01 UTC
Message-ID
<xmqqsggfe23v.fsf@gitster.c.googlers.com>
In-Reply-To
<20200504220517.GE45250@syl.local>
Taylor Blau <me@ttaylorr.com> writes:
Show 13 quoted lines
> 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).

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.

Previous: Taylor BlauNext: Taylor Blau
Message 5 of 6 in “tig: bug when binding to 'generic'?”
  1. Wolfram SangMay 2, 2020
  2. Kevin DaudtMay 2, 2020
  3. Wolfram SangMay 2, 2020
  4. Taylor BlauMay 4, 2020
  5. Junio C HamanoMay 4, 2020
  6. Taylor BlauMay 4, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.