From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9front@9front.org
Subject: [9front] 9front, git and mercurial.
Date: Wed, 18 May 2022 15:48:13 -0400 [thread overview]
Message-ID: <fafcd932-d1bd-3b27-a1ba-f71237923060@fjrhome.net> (raw)
In-Reply-To: <dbbd3656-69c9-b71b-2d08-07912ad5326d@fjrhome.net>
New here - moving this discussion from the 9fans mailing list.
On 5/18/22 3:41 PM, Frank D. Engel, Jr. wrote:
> I didn't even notice until now that there was a dedicated 9front list
> - I will try to subscribe to that shortly and move the conversation
> there.
>
> Not sure that I understand how to determine which revision I am on -
> more familiar with svn than either hg or git - if I run "hg log"
> within /sys/src the first two lines say:
>
>
> changeset: 8493:c8bec6f5ee1e
>
> tag: tip
>
>
> Does that answer the question, or how do I go about obtaining that?
>
>
>
> On 5/18/22 2:30 PM, Kurt H Maier via 9fans wrote:
>> On Wed, May 18, 2022 at 02:12:47PM -0400, Frank D. Engel, Jr. wrote:
>>> Related question I can't seem to track down an answer to:
>>>
>>> I have a 9front cluster which was set up back when Mercurial was used,
>>> so that is what sysupdate is looking for.
>>>
>>> I finally realized that I am no longer seeing updates because 9front
>>> switched to git.
>>>
>>> How does one go about upgrading an existing 9front install to pull
>>> updates from git instead of hg?
>> sysupdate should have seamlessly moved you to git. what mercurial
>> revision is your stuff currently running?
>>
>> this will be a longish debugging session so for the rest of it we should
>> probably move to the 9front mailing list, since 9fans at large might not
>> appreciate the traffic.
>>
>> khm
>
> ------------------------------------------
> 9fans: 9fans
> Permalink:
> https://9fans.topicbox.com/groups/9fans/T7dfa66085e395bcb-Mb037360ea191ed4fde0a87aa
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>
next parent reply other threads:[~2022-05-18 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <89F3ABF218EE52FAE7605F9B07728487@eigenstate.org>
[not found] ` <1275338a-65f0-61c2-8162-ba7c93fa2493@fjrhome.net>
[not found] ` <YoU7OpruuHGcQYUj@wopr>
[not found] ` <dbbd3656-69c9-b71b-2d08-07912ad5326d@fjrhome.net>
2022-05-18 19:48 ` Frank D. Engel, Jr. [this message]
2022-05-18 20:03 ` Frank D. Engel, Jr.
2022-05-19 1:51 ` ori
2022-05-19 8:20 ` Frank D. Engel, Jr.
2022-05-19 17:46 ` Kurt H Maier
2022-05-19 18:41 ` Frank D. Engel, Jr.
2022-05-20 1:33 ` Jacob Moody
2022-05-20 2:25 ` Frank D. Engel, Jr.
2022-05-20 4:37 ` ori
2022-05-20 9:15 ` Frank D. Engel, Jr.
2022-05-20 14:30 ` ori
2022-05-20 15:00 ` Frank D. Engel, Jr.
2022-05-20 1:02 ` Amavect
2022-05-20 2:35 ` Frank D. Engel, Jr.
2022-05-20 2:59 ` Jacob Moody
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=fafcd932-d1bd-3b27-a1ba-f71237923060@fjrhome.net \
--to=fde101@fjrhome.net \
--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).