9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] Some trash in the src tree
Date: Mon, 12 Feb 2024 01:11:36 +0100	[thread overview]
Message-ID: <9F445CCA1B9B4EBE8AA7A64FC16EB3DB@wopr.sciops.net> (raw)
In-Reply-To: <74D28144E2431926A1A5EE500E11670C@eigenstate.org>

On Sun Feb 11 23:13:09 +0100 2024, ori@eigenstate.org wrote:
> Removing it from the source tree doesn't remove it from the git history :)
> 
> The main problem is that if there's a precompiled binary, I don't know
> how diff/patch will deal with it as things stand.
> 
> Quoth an2qzavok@gmail.com:
> > I've been grepping the source for some reason and found /sys/src/cmd/tcs/font
> > Not only files there appear to never be referenced in tcs itself, it even 
> > contains a pre-compiled mips binary 'merge'.
> > Also, font/ code won't even complie due to missing 'libg.h' header.
> > 
> > I am a bit reluctant about sending plain removal patch though, what if it has 
> > some significant historical value? It looks like some font manipulating/
> > converting programs.

Seems like the font/ subdirectory is old and afaik undocumented 2e
code that hasn't been touched since that release as libg.h is already
missing in 3e.  From a quick glance, these might have been used to
generate some of the fonts in /lib/font.  Unless there's some utility
in porting this code, I suggest we just remove the directory.

Cheers,
qwx

      reply	other threads:[~2024-02-12  0:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11 18:47 an2qzavok
2024-02-11 22:12 ` ori
2024-02-12  0:11   ` qwx [this message]

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=9F445CCA1B9B4EBE8AA7A64FC16EB3DB@wopr.sciops.net \
    --to=qwx@sciops.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).