From: Ben Woodard <woodard@redhat.com>
To: Dodji Seketeli <dodji@seketeli.org>
Cc: Ben Woodard via Libabigail <libabigail@sourceware.org>,
"Sochat, Vanessa" <sochat1@llnl.gov>
Subject: Re: [PATCH] V2 Add github actions to support workflows
Date: Mon, 16 May 2022 08:37:47 -0700 [thread overview]
Message-ID: <7B10B94D-0431-4CFE-803B-0031A873D875@redhat.com> (raw)
In-Reply-To: <87wnepvngx.fsf@seketeli.org>
> On May 13, 2022, at 1:35 AM, Dodji Seketeli <dodji@seketeli.org> wrote:
>
> Hello Ben, Vanessa,
>
> Ben Woodard via Libabigail <libabigail@sourceware.org> a écrit:
>
> [...]
>
>> Signed-off-by: vsoch <vsoch@users.noreply.github.com>
>
> Would you please put the complete name of Vanessa in here? Just like
> what we have for:
>
>> Reviewed-by: Ben Woodard <woodard@redhat.com>
>
> Also, is vsoch@users.noreply.github.com a valid email? My mail user
> agent keeps nagging me about it, so I thought I'd ask if the email is
> valid.
>
Yeah I noticed that. That was the way the patch came to me and so I didn’t want to take the liberty to change it. I’ll swap in email address that I commiunicate with her and run it by her to make sure that is the one that she wants to use.
>
>> ---
>> .github/workflows/build-container.yaml | 99 +++++++++++++++++++
>
> Also, would it be possible to add a little text in .github pointing to
> the online doc where people can learn about this github workflow
> business? We can add that alter in any case. I am happy to commit this
> patch as is right now, assuming the naming issue of the signed-off-by
> tag is addressed.
>
No problem.
> Thanks!
>
> Cheers,
>
> --
> Dodji
>
prev parent reply other threads:[~2022-05-16 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 17:32 Ben Woodard
2022-05-13 8:35 ` Dodji Seketeli
2022-05-16 15:37 ` Ben Woodard [this message]
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=7B10B94D-0431-4CFE-803B-0031A873D875@redhat.com \
--to=woodard@redhat.com \
--cc=dodji@seketeli.org \
--cc=libabigail@sourceware.org \
--cc=sochat1@llnl.gov \
/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).