From: Ingo Schwarze <firstname.lastname@example.org> To: Simon Branch <email@example.com> Cc: firstname.lastname@example.org Subject: Re: tbl: incorrect width calculation in cs[s..] Date: Sat, 9 Apr 2022 19:58:45 +0200 [thread overview] Message-ID: <YlHJVRcwScVAR2ka@asta-kit.de> (raw) In-Reply-To: <email@example.com> Hi Simon, Simon Branch wrote on Sat, Apr 09, 2022 at 10:35:26AM -0700: > 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 Right, mouse-based copy and paste is one of the typical ways how people mangle patches without even noticing it. > (discarded because > I hadn't been let into the mailing list yet) was the culprit. No real problem caused in this case. Let's be happy happy you gained this experience with a small patch rather than with a large one. :-) > I'm still getting used to the mailing list workflow ... Of course, every workflow needs getting used to, but in absolute terms, i think that mailing list worflows are significantly simpler and *much* less error prone than web-based workflows. Even though i avoid web-based workflows whereever possible, the number of instances where i had to write text twice because information had to be put into some web form which then crashed in the middle of assembling the information are too numerous to count. > Thank you for all your work on mandoc and OpenBSD! You are welcome, thank you very much for reporting problems and even more for sending in a very good patch. Yours, Ingo -- To unsubscribe send an email to firstname.lastname@example.org
prev parent reply other threads:[~2022-04-09 17:58 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 2022-04-09 17:58 ` Ingo Schwarze [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=YlHJVRcwScVAR2ka@asta-kit.de \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: tbl: incorrect width calculation in cs[s..]' \ /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).