From: "pabs3 at bonedaddy dot net" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29618] Archive projects at Software Heritage
Date: Tue, 06 Jun 2023 01:03:28 +0000 [thread overview]
Message-ID: <bug-29618-14326-wFva7JBcXu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29618-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29618
--- Comment #9 from Paul Wise <pabs3 at bonedaddy dot net> ---
Yeah, the SWH folks said on IRC that the CVS archiving expects an rsync URL.
The current status is now:
Regular forge listing and repo archiving enabled for all four cgit instances.
All the git repositories on sourceware.org/cgit that I submitted already got
archived. I noticed that I missed the cygwin-apps ones there though, submitting
them now.
All the git repositories on gcc.gnu.org/cgit and git.dwarfstd.org that I
submitted got archived.
The submissions for cygwin.com/cgit are still ongoing.
The submissions for sourceware.org SVN repos: all accepted, kawa/prelink
finished, gcc ongoing.
The submissions for sourceware CVS repos are still ongoing.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-06-06 1:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 13:24 [Bug Infrastructure/29618] New: " mark at klomp dot org
2023-05-16 9:43 ` [Bug Infrastructure/29618] " pabs3 at bonedaddy dot net
2023-05-16 9:44 ` pabs3 at bonedaddy dot net
2023-06-04 17:52 ` mark at klomp dot org
2023-06-04 18:03 ` mark at klomp dot org
2023-06-04 18:15 ` mark at klomp dot org
2023-06-05 0:45 ` pabs3 at bonedaddy dot net
2023-06-05 18:41 ` joseph at codesourcery dot com
2023-06-05 20:02 ` mark at klomp dot org
2023-06-06 1:03 ` pabs3 at bonedaddy dot net [this message]
2023-06-10 1:12 ` pabs3 at bonedaddy dot net
2023-06-10 1:40 ` pabs3 at bonedaddy dot net
2023-06-10 1:41 ` pabs3 at bonedaddy dot net
2023-06-10 1:41 ` pabs3 at bonedaddy dot net
2023-06-10 1:54 ` pabs3 at bonedaddy dot net
2023-06-10 1:58 ` pabs3 at bonedaddy dot net
2023-06-23 19:45 ` mark at klomp dot org
2023-06-24 1:41 ` pabs3 at bonedaddy dot net
2023-07-24 19:12 ` fche at redhat dot com
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=bug-29618-14326-wFva7JBcXu@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.org \
/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).