9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] pstree binary not removed after being reimplemented in awk
Date: Sat, 16 Nov 2024 18:26:09 +0200	[thread overview]
Message-ID: <CAJ1xhMUz642Kge=5V=6J5h9FV7X988FZMykuy96zqtceepxzRQ@mail.gmail.com> (raw)
In-Reply-To: <7497BB380B440C3D54B4F12EE9C102C7@wopr.sciops.net>

On Sat, 16 Nov 2024 at 17:48, <qwx@sciops.net> wrote:
>
> On Sat Nov 16 16:33:50 +0100 2024, alexander.kapshuk@gmail.com wrote:
> > Commit 493bac79b63f1949a29aeec8270fab4a599a6ee3, pstree: reimplement
> > in awk, optionally restrict to a given process, has removed the C
> > source file, but not the binary.
> >
> > cpu% file /bin/pstree
> > /bin/pstree: amd64 plan 9 executable
> >
> > Is that intentional?
>
> The binaries are not tracked in the git repo, and there currently is no
> mechanism in place to remove binaries replaced by scripts -- so in
> that sense, yes, this is expected.  The laziest way would be `rm
> /*/bin/pstree; bind -ac /dist/plan9front /; git/revert /rc/bin/pstree`
> or something like that.  Sorry for the inconvenience, though this does
> not happen often.
>
> Cheers,
> qwx

Thanks for a prompt reply.
No inconvenience caused whatsoever.

With the old binary out of the way, it's the awk version that is
reported by the file command:
cpu% file /bin/pstree
/bin/pstree: rc executable file

      reply	other threads:[~2024-11-16 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16 15:32 Alexander Kapshuk
2024-11-16 15:47 ` qwx
2024-11-16 16:26   ` Alexander Kapshuk [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='CAJ1xhMUz642Kge=5V=6J5h9FV7X988FZMykuy96zqtceepxzRQ@mail.gmail.com' \
    --to=alexander.kapshuk@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).