9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: Stanley Lieber <9front@9front.org>
Subject: AW: [9front] Two errors in fqa
Date: Sun, 20 Jun 2021 07:08:19 +0000 (UTC)	[thread overview]
Message-ID: <7f1d0806-1648-449e-88b4-c0b2326798dc@sirjofri.de> (raw)
In-Reply-To: <C9E6B5F8-CF00-4EBC-AA63-641D7ED4627D@stanleylieber.com>


19.06.2021 17:49:52 Stanley Lieber <sl@stanleylieber.com>:
> On June 19, 2021 3:29:17 AM EDT, sirjofri 
> <sirjofri+ml-9front@sirjofri.de> wrote:
>> Hello all,
>>
>> I just found two errors in fqa (the online html version):
>
> thanks!
>
>
>> 1.3.0.1: The url to "They Live and the secret history of the Mozilla
>> logo" doesn't work. It starts with a `"` and therefore leads to
>> http://fqa.9front.org/.../"https://...
>
> can reproduce the failure in firefox, but I don't see the leading ". 
> the html looks correct, I can't understand why it renders the way it 
> does. any ideas?

This is the exact URL I get when copying the URL in chrome on android:

http://fqa.9front.org/%E2%80%9Dhttps://www.jwz.org/blog/2016/10/they-live-and-the-secret-history-of-the-mozilla-logo/%22

I looked at the source and it's:

<a href=”https

Note that the rune ” is used instead of ascii ".

>> 1.3.1: source updates are done with ~~hg(1) (Mercurial)~~ git(1)
>>
>
> I didn't have any warning we were switching to git right away. the fqa 
> still refers to hg throughout. I'm working on it.

When sysupdating with sysupdate it fetches the last update from hg, which 
contains git9 and a new version of sysupdate itself. This new sysupdate 
(after mk install) fetches the .git seed directory, which allows to fetch 
the new updates into /dist/plan9front. All following sysupdates work like 
before, but using git9 instead of hg.

I don't know what exactly is the plan, but that's at least what I get as 
a normal user with sysupdate. If in doubt, ask ori? I haven't been very 
active in the community lately due to work and Unreal Engine 5.

sirjofri

  reply	other threads:[~2021-06-20 10:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19  7:29 sirjofri
2021-06-19 15:49 ` Stanley Lieber
2021-06-20  7:08   ` sirjofri [this message]
2021-06-20 15:19     ` Stanley Lieber
2021-06-20 16:33       ` cinap_lenrek
2021-06-21  1:33         ` sl
2021-06-20 20:06       ` AW: " sirjofri
2021-06-20 23:46         ` Stanley Lieber
2021-06-20 13:28   ` ori
2021-06-21  1:32     ` sl
2021-06-21  1:57       ` ori
2021-06-24 22:26   ` Stuart Morrow
2021-06-25  0:03     ` Stanley Lieber
2021-06-25 18:03       ` Sigrid Solveig Haflínudóttir
2021-06-25 18:35         ` Stanley Lieber
2021-06-25 18:39         ` hiro
2021-06-25  0:24     ` Kurt H Maier
2021-06-25 11:16       ` Stuart Morrow
2021-06-25 13:52         ` Sigrid Solveig Haflínudóttir
2021-06-25 18:09         ` Kurt H Maier
     [not found]           ` <fbbb68c4-8d65-4c08-a59f-0a73208dfb36@a-b.xyz>
2021-06-25 23:11             ` Stanley Lieber
2021-06-26  8:25               ` kvik
2021-06-28 18:12                 ` kvik
2021-06-28 18:21                   ` Kurt H Maier
2021-06-28 20:14                   ` sl

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=7f1d0806-1648-449e-88b4-c0b2326798dc@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --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).