lttng-dev Archive mirror
 help / color / mirror / Atom feed
From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: Paul Wise <archival@softwareheritage.org>,
	LTTng development <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Software Heritage archival notification for git.liburcu.org
Date: Mon, 15 Apr 2024 10:20:58 -0400	[thread overview]
Message-ID: <edd5722d-8103-4ef0-a53e-58d8d03ed928@efficios.com> (raw)
In-Reply-To: <d1d8d46ef56ca05206ca673804cbd651eeacc4e5.camel@softwareheritage.org>

On 2024-04-14 20:39, Paul Wise wrote:
> On Thu, 2024-04-11 at 13:45 -0400, Michael Jeanson wrote:
> 
>> I see no issues with this, thanks for the heads-up.
> 
> PS: I note that git.liburcu.org and git.lttng.org seem to have
> identical contents. I wonder if SWH should be archiving just one of
> them or if we should archive both just in case they get split up?

At the moment 'git.liburu.org' is just a CNAME for 'git.lttng.org', we don't 
have plans to split them up so far.

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

  parent reply	other threads:[~2024-04-15 14: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
     [not found]   ` <d1d8d46ef56ca05206ca673804cbd651eeacc4e5.camel@softwareheritage.org>
2024-04-15 14:20     ` Michael Jeanson via lttng-dev [this message]
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=edd5722d-8103-4ef0-a53e-58d8d03ed928@efficios.com \
    --to=lttng-dev@lists.lttng.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).