From: Erik Christiansen <erik@dd.nec.com.au>
To: Jan Beulich <JBeulich@novell.com>
Cc: binutils@sources.redhat.com
Subject: Re: macro behavior
Date: Fri, 15 Apr 2005 08:32:00 -0000 [thread overview]
Message-ID: <20050415083022.GC846@dd.nec.com.au> (raw)
In-Reply-To: <s25f7070.029@emea1-mh.id2.novell.com>
On Fri, Apr 15, 2005 at 08:42:46AM +0200, Jan Beulich wrote:
>
> Zack's suggestion seems very promising to me, though.
Yes, his suggestion is clearly going to solve ambiguity problems which
arise with the implicit appending that I've been using.
> I'll look into whether that can be implemented without caveats.
That shell-like syntax would be a kindness to posterity. :-)
Erik
next parent reply other threads:[~2005-04-15 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s25f7070.029@emea1-mh.id2.novell.com>
2005-04-15 8:32 ` Erik Christiansen [this message]
2005-04-20 9:20 Jan Beulich
2005-04-20 9:34 ` Hans-Peter Nilsson
-- strict thread matches above, loose matches on Subject: below --
2005-04-15 6:42 Jan Beulich
2005-04-14 14:43 Jan Beulich
2005-04-14 17:25 ` Zack Weinberg
2005-04-15 2:49 ` Erik Christiansen
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=20050415083022.GC846@dd.nec.com.au \
--to=erik@dd.nec.com.au \
--cc=JBeulich@novell.com \
--cc=binutils@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).