git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Wolfram Sang <wsa@the-dreams.de>, Kevin Daudt <me@ikke.info>,
	Wolfram Sang <wsa@kernel.org>,
	git@vger.kernel.org, Thomas Koutcher <thomas.koutcher@online.fr>,
	Jonas Fonseca <jonas.fonseca@gmail.com>
Subject: Re: tig: bug when binding to 'generic'?
Date: Mon, 04 May 2020 16:01:40 -0700	[thread overview]
Message-ID: <xmqqsggfe23v.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200504220517.GE45250@syl.local> (Taylor Blau's message of "Mon, 4 May 2020 16:05:17 -0600")

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).

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.

  reply	other threads:[~2020-05-04 23:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 19:04 tig: bug when binding to 'generic'? Wolfram Sang
2020-05-02 19:07 ` Kevin Daudt
2020-05-02 19:31   ` Wolfram Sang
2020-05-04 22:05     ` Taylor Blau
2020-05-04 23:01       ` Junio C Hamano [this message]
2020-05-04 23:14         ` Taylor Blau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqsggfe23v.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jonas.fonseca@gmail.com \
    --cc=me@ikke.info \
    --cc=me@ttaylorr.com \
    --cc=thomas.koutcher@online.fr \
    --cc=wsa@kernel.org \
    --cc=wsa@the-dreams.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).