From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, Taylor Blau <me@ttaylorr.com>,
git@vger.kernel.org
Subject: Re: Random GitHub Actions added to git/git???
Date: Mon, 19 Apr 2021 20:41:32 -0400 [thread overview]
Message-ID: <YH4jPMPrLA+a85RH@nand.local> (raw)
In-Reply-To: <xmqqmttt7q8f.fsf@gitster.g>
On Mon, Apr 19, 2021 at 05:29:36PM -0700, Junio C Hamano wrote:
> I suspect that these other ones come from "pull requests" random
> people threw at us that never hit our tree, with changes to the
> .github/workflows/ directory in these PR.
>
> I find them quite distracting.
That's what I'd expect, too, but I'm not sure. I asked the people who
would know, and I'll reply back here once I have an answer.
> Thanks.
Thanks,
Taylor
next prev parent reply other threads:[~2021-04-20 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 0:29 Random GitHub Actions added to git/git??? Junio C Hamano
2021-04-20 0:41 ` Taylor Blau [this message]
2021-04-20 16:23 ` Taylor Blau
2021-04-20 9:48 ` Bagas Sanjaya
2021-04-20 15:55 ` Johannes Schindelin
2021-04-20 15:51 ` Johannes Schindelin
2021-04-20 20:23 ` Junio C Hamano
2021-04-21 12:38 ` Johannes Schindelin
2021-04-21 23:05 ` Junio C Hamano
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=YH4jPMPrLA+a85RH@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.