From: Xiao-Yong Jin <meta.jxy@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] BitBucket deleting hg repos
Date: Thu, 2 Jul 2020 14:16:27 -0500 [thread overview]
Message-ID: <189CA348-86E5-4450-8735-44424F3A94FD@gmail.com> (raw)
In-Reply-To: <0DACB053D74C6972E17498DAB4CBEC12@eigenstate.org>
Can you share the set of software and the workflow you used
for the hg to git conversion?
> On Jul 2, 2020, at 9:47 AM, ori@eigenstate.org wrote:
>
>> yup: https://github.com/Plan9-Archive
>>
>> On Thu, Jul 2, 2020 at 3:47 PM raingloom <raingloom@riseup.net> wrote:
>>>
>>> I just learned about this today. There are a lot of Plan 9 related
>>> repos there. Are they backed up anywhere?
>
> If you find any that aren't, of course, please make sure that we get
> them in!
next prev parent reply other threads:[~2020-07-02 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 13:47 raingloom
2020-07-02 14:26 ` [9fans] " Rodrigo G. López
2020-07-02 14:47 ` ori
2020-07-02 19:16 ` Xiao-Yong Jin [this message]
2020-07-02 19:27 ` ori
2020-07-02 21:05 ` Sean Hinchee
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=189CA348-86E5-4450-8735-44424F3A94FD@gmail.com \
--to=meta.jxy@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).