From: Taylor Blau <me@ttaylorr.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: 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, 4 May 2020 16:05:17 -0600 [thread overview]
Message-ID: <20200504220517.GE45250@syl.local> (raw)
In-Reply-To: <20200502193102.GA1160@kunai>
On Sat, May 02, 2020 at 09:31:02PM +0200, Wolfram Sang wrote:
> Hi Kevin,
>
> > Tig is a third-party interface, not maintained by git. You can report
> > issues for tig on [github][0]
>
> I know it is third-party. Seems the README in tig needs fixing, too:
>
> ===
> Bugs and feature requests can be reported using the issue tracker or by
> mail to either the Git mailing list or directly to the maintainer.
> ==
>
> I prefer the mail option, so I wrote here and CCed the maintainers.
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.
> Kind regards,
>
> Wolfram
>
Thanks,
Taylor
next prev parent reply other threads:[~2020-05-04 22:05 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 [this message]
2020-05-04 23:01 ` Junio C Hamano
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=20200504220517.GE45250@syl.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=jonas.fonseca@gmail.com \
--cc=me@ikke.info \
--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).