From: Mark Wielaard <mark@klomp.org>
To: Ben Woodard <woodard@redhat.com>
Cc: libabigail@sourceware.org, vsoch <vsoch@users.noreply.github.com>
Subject: Re: [PATCH] Add github actions to support workflows
Date: Sat, 30 Apr 2022 22:08:09 +0200 [thread overview]
Message-ID: <20220430200809.GB11996@gnu.wildebeest.org> (raw)
In-Reply-To: <20220422161716.710496-1-woodard@redhat.com>
Hi Ben,
On Fri, Apr 22, 2022 at 09:17:16AM -0700, Ben Woodard via Libabigail wrote:
[ ... application/octet-stream ...]
Aha, there are those scripts and container files. But sending the
patches as application/octet-stream causes them to be hidden in my mua
(mutt).
I'll leave the "workflow" stuff to someone who doesn't think github is
a major PITA. But I think you should submit the tools/fedabipkgdiff
change separately. It looks correct to me.
Thanks,
Mark
next prev parent reply other threads:[~2022-04-30 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 16:17 Ben Woodard
2022-04-30 20:08 ` Mark Wielaard [this message]
2022-05-03 0:18 ` Ben Woodard
2022-05-03 10:52 ` David Marchand
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=20220430200809.GB11996@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=libabigail@sourceware.org \
--cc=vsoch@users.noreply.github.com \
--cc=woodard@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).