From: email@example.com To: firstname.lastname@example.org Subject: Re: [9front] rc redirect error messages Date: Tue, 10 May 2022 22:49:06 +0200 [thread overview] Message-ID: <31A7B19179FF68635CDBB0550B2C4847@wopr.sciops.net> (raw) In-Reply-To: <0F30FE85BF79F831B8711AC48BB2F0A9@prosimetrum.com> On Mon May 9 22:24:56 +0200 2022, email@example.com wrote: > I always have to remind myself which way round, > and today while doing so I saw these ones which > have it wrong (should be >[1=2]): > > /rc/bin/Bfn:4: echo usage: $0 fn >[2=1] > /rc/bin/Bfn:15: echo $1: not found >[2=1] > /rc/bin/ipso:69: echo >[2=1] 'usage: ipso [-a -f -e -l] [-s] [file ...]' > /rc/bin/ipso:88: echo >[2=1] ipso: must specify a fully qualified file name for aescbc '(-a)' > > A quick fix someone with commit access could apply. > > Thanks, > > umbraticus Pushed with a few others I found. Thanks! Cheers, qwx
next prev parent reply other threads:[~2022-05-10 20:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-09 20:24 umbraticus 2022-05-10 20:49 ` qwx [this message] 2022-05-11 9:55 ` umbraticus
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=31A7B19179FF68635CDBB0550B2C4847@wopr.sciops.net \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [9front] rc redirect error messages' \ /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
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).