Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: add-forge-now+981.2T8mQOR3uawEg4qPiymRBTnyh9w@archive.softwareheritage.org,
	 Software Heritage Archival Moderators
	<archival@softwareheritage.org>,
	LTTng development <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Software Heritage archival notification for git.liburcu.org
Date: Thu, 11 Apr 2024 13:45:36 -0400	[thread overview]
Message-ID: <7bacc8ff-c7b8-43ac-89e0-c3036131e1c8@efficios.com> (raw)
In-Reply-To: <dcdc31d82b68d1ecff6555f67b6a7c8f6b7032ad.camel@softwareheritage.org>

On 2024-04-10 22:37, Paul Wise via lttng-dev wrote:
> Hello liburcu developers,
> 
> The mission of Software Heritage is to collect, preserve and share all
> the publicly available source code: https://www.softwareheritage.org
> 
> We have received a request to add the forge hosted at the URL below
> to the list of software origins that are archived, and it is our
> understanding that you are or know the contact person for this forge.
> 
> https://git.liburcu.org/
> 
> In order to archive the forge contents, we will have to periodically
> pull the public repositories it contains and clone them into the
> Software Heritage archive. FAQs for our processes are available:
> 
> https://docs.softwareheritage.org/user/faq/#add-forge-now
> https://www.softwareheritage.org/faq/
> 
> Please let us know if there are any issues to consider before
> we launch the archival of the public repositories hosted on your
> infrastructure. Please use "Reply all" to ensure our system will
> process your answer properly.
> 
> In the absence of an answer to this message, we will start to archive
> your forge in the coming weeks. Only the publicly accessible
> repositories will be archived.
> 
> Thank you in advance for your help.
> 
> Kind regards,
> The Software Heritage team
> 

Hi,

I see no issues with this, thanks for the heads-up.

Michael
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  reply	other threads:[~2024-04-11 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  2:37 Paul Wise via lttng-dev
2024-04-11 17:45 ` Michael Jeanson via lttng-dev [this message]
2024-04-12  0:20   ` Paul Wise via lttng-dev
     [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=7bacc8ff-c7b8-43ac-89e0-c3036131e1c8@efficios.com \
    --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