From: Xiao-Yong Jin <meta.jxy@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] moving to git
Date: Mon, 7 Jun 2021 14:18:46 -0500 [thread overview]
Message-ID: <2EE39354-0BF2-4DF4-B158-05BB0AA7F3C8@gmail.com> (raw)
In-Reply-To: <9C7C2E3FB35376F259797556A945821C@eigenstate.org>
> On Jun 6, 2021, at 5:11 PM, ori@eigenstate.org wrote:
>
> Quoth ori@eigenstate.org:
>> We're moving our over to git, hosted on 9front:
>>
>> http://git.9front.org
>>
>> To move your system over, run sysupdate twice.
>
>
> Git had some bugs that would clobber files on merge.
> Including itself.
>
> It be fixed
What would happen to local changes if I run sysupdate twice?
Particularly, for
(1) local uncommitted changes;
(2) local commits in hg.
What would be the recommended steps to preserve the locally
uncommitted and committed changes?
next prev parent reply other threads:[~2021-06-07 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 14:19 ori
2021-06-05 14:34 ` ori
2021-06-06 0:04 ` cinap_lenrek
2021-06-06 18:36 ` adr
2021-06-05 17:51 ` Steffen Nurpmeso
2021-06-06 22:11 ` ori
2021-06-06 23:07 ` ori
2021-06-07 19:18 ` Xiao-Yong Jin [this message]
2021-06-07 20:42 ` ori
2021-06-10 1:34 ` Xiao-Yong Jin
2021-06-28 18:07 ` Stuart Morrow
2021-06-28 18:15 ` Kurt H Maier
2021-06-28 18:34 ` ori
2021-06-28 18:47 ` Stuart Morrow
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=2EE39354-0BF2-4DF4-B158-05BB0AA7F3C8@gmail.com \
--to=meta.jxy@gmail.com \
--cc=9front@9front.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 NNTP newsgroup(s).