From: Paul Wise via lttng-dev <lttng-dev@lists.lttng.org>
To: Michael Jeanson <mjeanson@efficios.com>,
add-forge-now+981.2T8mQOR3uawEg4qPiymRBTnyh9w@archive.softwareheritage.org,
LTTng development <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Software Heritage archival notification for git.liburcu.org
Date: Fri, 12 Apr 2024 08:20:59 +0800 [thread overview]
Message-ID: <862eb7a4a6ae7141803100b6149b632be50e71e3.camel@softwareheritage.org> (raw)
In-Reply-To: <7bacc8ff-c7b8-43ac-89e0-c3036131e1c8@efficios.com>
On Thu, 2024-04-11 at 13:45 -0400, Michael Jeanson wrote:
> I see no issues with this, thanks for the heads-up.
Great. I have started the initial archiving, you can follow it here:
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/issues/368
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/pipelines/8317/builds
--
bye,
pabs
https://wiki.softwareheritage.org/wiki/User:PaulWise
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2024-04-12 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 2:37 [lttng-dev] Software Heritage archival notification for git.liburcu.org Paul Wise via lttng-dev
2024-04-11 17:45 ` Michael Jeanson via lttng-dev
2024-04-12 0:20 ` Paul Wise via lttng-dev [this message]
[not found] ` <d1d8d46ef56ca05206ca673804cbd651eeacc4e5.camel@softwareheritage.org>
2024-04-15 14:20 ` Michael Jeanson via lttng-dev
2024-04-15 14:33 ` Mathieu Desnoyers via lttng-dev
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=862eb7a4a6ae7141803100b6149b632be50e71e3.camel@softwareheritage.org \
--to=lttng-dev@lists.lttng.org \
--cc=add-forge-now+981.2T8mQOR3uawEg4qPiymRBTnyh9w@archive.softwareheritage.org \
--cc=archival@softwareheritage.org \
--cc=mjeanson@efficios.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).