From: Todd Zullinger <tmz@pobox.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, Drew Northup <drew.northup@maine.edu>,
Andi Kleen <andi@firstfloor.org>,
Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, Chris Johnsen <chris_johnsen@pobox.com>
Subject: Re: groff .ft command use in asciidoc
Date: Fri, 19 Nov 2010 20:48:09 -0500 [thread overview]
Message-ID: <20101120014808.GZ16929@inocybe.localdomain> (raw)
In-Reply-To: <7v62vsc45d.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
Junio C Hamano wrote:
> Thanks. I usually am fairly cautious when changing the default, but
> I think this particular one is not such a big deal. I agree that
> the end of the year release would probably be a good time to switch.
>
> I think people on RHEL5 would also be ok; they have paid support for
> this kind of thing, no ;-)?
Sadly, git isn't in RHEL5 officially. We package it in EPEL though.
Currently, it's at the ancient 1.5.5.6 mile marker. I have taken care
to ensure that the Fedora rpm's build cleanly for EPEL-5 (and 4 last I
checked), albeit with the lack of emacs support¹.
I haven't tested this patch, but I am confident that removing the
ASCIIDOC knobs where appropriate won't cause us any grief in Fedora,
EPEL, or RHEL (where git-1.7.x is now officially supported, finally!).
¹ Incidentally, if anyone here is a strong user of emacs vcs mode and
could help work out what we need to do to make git-1.7.x work with the
emacs-21.4 shipped in RHEL, please let me know. That's the only
impediment (that I know of) keeping us from moving EPEL to a more
modern git, with all the fabulous advantages the fine folks here have
made since 1.5.x.
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Happiness, n.: An agreeable sensation arising from contemplating the
misery of another.
-- Ambrose Bierce, "The Devil's Dictionary"
[-- Attachment #2: Type: application/pgp-signature, Size: 542 bytes --]
next prev parent reply other threads:[~2010-11-20 1:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 9:52 groff .ft command use in asciidoc Andi Kleen
2010-11-17 10:15 ` Jonathan Nieder
2010-11-17 11:52 ` Andi Kleen
2010-11-17 14:38 ` Jeff King
2010-11-17 15:48 ` Andi Kleen
2010-11-19 17:54 ` Jeff King
2010-11-19 18:22 ` Jonathan Nieder
2010-11-19 18:37 ` Jeff King
2010-11-19 20:34 ` Drew Northup
2010-11-19 20:40 ` Jeff King
2010-11-19 20:53 ` Drew Northup
2010-11-19 22:58 ` Junio C Hamano
2010-11-20 1:48 ` Todd Zullinger [this message]
2010-11-18 17:47 ` Alejandro Riveira Fernández
2010-11-18 21:11 ` Drew Northup
2010-11-18 23:15 ` Alejandro Riveira Fernández
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=20101120014808.GZ16929@inocybe.localdomain \
--to=tmz@pobox.com \
--cc=andi@firstfloor.org \
--cc=chris_johnsen@pobox.com \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/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