Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: "Miles Bader" <miles@gnu.org>
Cc: <ding@gnus.org>
Subject: Re: etc/refcards/ and new-style backquotes
Date: Fri, 31 Aug 2007 01:07:00 +0200	[thread overview]
Message-ID: <v93ay01v1n.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <fc339e4a0708291925u5f51fdfen1985b49097d6492@mail.gmail.com> (Miles Bader's message of "Thu, 30 Aug 2007 11:25:33 +0900")

[ I've split off the general merge topic and this specific issue.]

In a personal mail, Miles Bader wrote:

> There are some other potentially troublesome changes, such as the
> removal of old-style backquotes, 

I didn't follow this discussion closely on emacs-devel.  Is it an
incompatible change WRT Emacs 21 (and XEmacs 21.[45])?  (At least a
quick `emacs-lisp-byte-compile-and-load' succeeded in Emacs 21.)

[The new-style backquotes change is also in emacs-rel-22 so it is
independent from how we proceed with merging.]

> and the refcards getting moved into etc/refcards (I don't know if
> this move is desirable for Gnus; if not, then just move them back,
> but if so, I guess the Makefiles etc will need adjusting?).  As this
> is the 5.10 branch, people might want to keep an eye out for
> problems.

Hm, the etc/ reorganization is only in Emacs trunk, isn't it.  Did you
sync from Emacs/trunk to Gnus/v5-10?

Given that we only have a couple of files in etc, I don't think we
need a separate directory for the Gnus refcard.  OTOH, I won't object
to it if it makes it more simple for you.  What do people think?

,----[ v5-10/etc$ cat CVS/Entries refcards/CVS/Entries ]
| /.cvsignore/6.1/Tue Jun 19 18:43:20 2001//Tv5-10
| D/smilies////
| D/images////
| /Makefile.in/1.5.2.9/Mon Jun  4 19:29:01 2007//Tv5-10
| /gnus-tut.txt/6.7.2.6/Mon Aug 27 07:07:35 2007//Tv5-10
| D/refcards////
| /README/1.1.2.1/Mon Aug 27 04:03:56 2007//Tv5-10
| /gnus-booklet.pdf/1.1.2.1/Mon Aug 27 04:03:56 2007//Tv5-10
| /gnus-logo.eps/1.1.2.1/Mon Aug 27 04:03:56 2007//Tv5-10
| /gnus-logo.pdf/1.1.2.1/Mon Aug 27 04:03:56 2007//Tv5-10
| /gnus-refcard.pdf/1.1.2.1/Mon Aug 27 04:03:56 2007//Tv5-10
| /gnus-refcard.tex/1.1.2.1/Mon Aug 27 04:03:56 2007//Tv5-10
| D
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  parent reply	other threads:[~2007-08-30 23:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <v96433px8i.fsf@marauder.physik.uni-ulm.de>
     [not found] ` <fc339e4a0708262100w957c4b3l5304f0ec34a63009@mail.gmail.com>
     [not found]   ` <v9lkbwacga.fsf@marauder.physik.uni-ulm.de>
2007-08-30  2:25     ` etc/refcards/ and new-style backquotes (was: Gnus and GPLv3) Miles Bader
2007-08-30 19:51       ` Leo
2007-08-31  1:42         ` etc/refcards/ and new-style backquotes Miles Bader
2007-08-31  6:39           ` Leo
2007-08-31  7:36             ` Miles Bader
2007-08-30 23:07       ` Reiner Steib [this message]
2007-08-30 23:16       ` Reiner Steib
2007-08-31  1:54         ` Miles Bader

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=v93ay01v1n.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=miles@gnu.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).