From: dsg@mitre.org (David S. Goldberg)
Subject: Re: Numbering invisible parts
Date: 31 Oct 1999 22:39:32 -0500 [thread overview]
Message-ID: <m1bu2n6283v.fsf@blackbird.mitre.org> (raw)
In-Reply-To: Hrvoje Niksic's message of "01 Nov 1999 01:36:26 +0100"
I don't care too much either way but it occurs to me that if inlined
parts that are not buttonized are not counted then the button numbers
have to change when someone does a K-b. I have to wonder if that
would cause any problems.
--
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
next prev parent reply other threads:[~1999-11-01 3:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-31 23:32 Hrvoje Niksic
1999-11-01 0:23 ` Kai Großjohann
1999-11-01 0:36 ` Hrvoje Niksic
1999-11-01 2:50 ` Shenghuo ZHU
1999-11-01 2:57 ` Hrvoje Niksic
1999-11-01 3:42 ` Shenghuo ZHU
1999-11-01 3:54 ` Hrvoje Niksic
1999-11-01 12:47 ` Steinar Bang
1999-11-01 3:39 ` David S. Goldberg [this message]
1999-11-01 3:43 ` Hrvoje Niksic
1999-11-01 4:22 ` Shenghuo ZHU
1999-11-07 0:34 ` Lars Magne Ingebrigtsen
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=m1bu2n6283v.fsf@blackbird.mitre.org \
--to=dsg@mitre.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).