From: malc@pulsesoft.com
To: git@vger.kernel.org
Subject: Re: [PATCH v2] Change octal literals to be XEmacs friendly
Date: Sat, 24 Jan 2009 17:18:19 +0300 [thread overview]
Message-ID: <873af8okic.fsf@linmac.oyster.ru> (raw)
In-Reply-To: 7v3af9p9lq.fsf@gitster.siamese.dyndns.org
Junio C Hamano <gitster@pobox.com> writes:
> malc@pulsesoft.com writes:
>
>> Kalle Olavi Niemitalo <kon@iki.fi> writes:
>>
>>> Vassili Karpov <av1474@comtv.ru> writes:
>>>
>>>> #ooctal syntax on the other hand produces integers everywhere.
>>>
>>> GNU Emacs 20.7 doesn't support #o, but neither does it include
>>
>> Bummer
>
> To be portable you could certainly spell them in decimal integers, no?
Sure.
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2009-01-24 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 23:20 [PATCH v2] Change octal literals to be XEmacs friendly Vassili Karpov
2009-01-24 1:31 ` Junio C Hamano
2009-01-24 1:46 ` Kalle Olavi Niemitalo
2009-01-24 2:01 ` malc
2009-01-24 5:16 ` Junio C Hamano
2009-01-24 14:18 ` malc [this message]
2009-01-26 22:59 ` Alexandre Julliard
-- strict thread matches above, loose matches on Subject: below --
2009-01-24 1:52 malc
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=873af8okic.fsf@linmac.oyster.ru \
--to=malc@pulsesoft.com \
--cc=git@vger.kernel.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).