From: Alyssa Ross <alyssa.ross@unikie.com>
To: devel@spectrum-os.org
Cc: Yuri Nesterov <yuriy.nesterov@unikie.com>
Subject: Re: [PATCH] img/live: add rootfs attribute passthru
Date: Fri, 23 Sep 2022 12:33:31 +0000 [thread overview]
Message-ID: <87a66qw9r8.fsf@alyssa.is> (raw)
In-Reply-To: <20220923122112.E01BE74509@atuin.qyliss.net>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
Alyssa Ross <qyliss@atuin.qyliss.net> writes:
> This patch has been committed as 0ca216d4ff06caa2ff6416e247c68f1e968d14d4,
> which can be viewed online at
> https://spectrum-os.org/git/spectrum/commit/?id=0ca216d4ff06caa2ff6416e247c68f1e968d14d4.
>
> This is an automated message. Send comments/questions/requests to:
> Alyssa Ross <hi@alyssa.is>
Just to explain what happened here for transparency: I noticed that I'd
accidentally dropped Yuri's authorship information from the commit, so I
did a quick force push to restore it.
(I know force pushes can be disruptive — I would not have done this if I
hadn't noticed /immediately/ after publishing. And the commit
notification bot does a nice job of making it clear and transparent what
happened — it might be nice to extend that to something that sent an
email every time a push happened, not just when a patch was taken from
devel@. Maybe to a separate list to avoid spamming people who're not
interested.)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2022-09-23 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 14:47 [PATCH] img/live: add rootfs attribute passthru Yuri Nesterov
2022-09-23 7:51 ` Ville Ilvonen
2022-09-23 10:10 ` Ivan Nikolaenko
2022-09-23 12:26 ` Ville Ilvonen
2022-09-23 12:16 ` Alyssa Ross
2022-09-23 12:20 ` Alyssa Ross
2022-09-23 12:21 ` Alyssa Ross
2022-09-23 12:33 ` Alyssa Ross [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=87a66qw9r8.fsf@alyssa.is \
--to=alyssa.ross@unikie.com \
--cc=devel@spectrum-os.org \
--cc=yuriy.nesterov@unikie.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.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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).