From: Simon Branch <simonmbranch@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mandoc.bsd.lv
Subject: Re: tbl: incorrect width calculation in cs[s..]
Date: Sat, 9 Apr 2022 10:35:26 -0700 [thread overview]
Message-ID: <20220409173526.dwy6e3dvd6ccxpcc@pine.sigxcpu.com> (raw)
In-Reply-To: <YlBqpfLzXa5+O+Mn@asta-kit.de>
On Fri, Apr 08, 2022 at 07:02:29PM +0200, Ingo Schwarze wrote:
> I had to apply your patch by hand because you converted tabs to
> spaces. When sending patches, please use "cvs diff -up" and make
> sure neither you nor your mail program mangle the patch.
Whoops, my naive copy-paste from my original email (discarded because
I hadn't been let into the mailing list yet) was the culprit. I'm
still getting used to the mailing list workflow ... Thank you for all
your work on mandoc and OpenBSD!
- Simon
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2022-04-09 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 20:14 Simon Branch
2022-04-08 17:02 ` Ingo Schwarze
2022-04-09 17:35 ` Simon Branch [this message]
2022-04-09 17:58 ` Ingo Schwarze
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=20220409173526.dwy6e3dvd6ccxpcc@pine.sigxcpu.com \
--to=simonmbranch@gmail.com \
--cc=discuss@mandoc.bsd.lv \
--cc=schwarze@usta.de \
/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).