all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: string-to-char
Date: Mon, 27 Nov 2006 21:13:38 +0100	[thread overview]
Message-ID: <f7ccd24b0611271213w4faf1ca6wf42937d713e13fb8@mail.gmail.com> (raw)
In-Reply-To: <17771.15699.17292.735995@kahikatea.snap.net.nz>

On 11/27/06, Nick Roberts <nickrob@snap.net.nz> wrote:

> Very probably.  The problem with changing them and the large numbers of files
> to which you are applying trivial fixes is that the code being pretested is no
> longer that in the repository.

Well, yeah, except that: 1) the changes I've done are really trivial
(you're right on that account) and it would be very surprising if they
broke something (and I'm assuming you're referring to the \s changes,
as the other are mostly doc fixes), and 2) the 22.0.91 pretest has not
been announced, AFAIK. At least, I'm in the pretester's list and
didn't receive any announce (I received one in the devel list). So I
don't think it's being tested, more or less than the CVS HEAD usually
is. I would not be doing changes if there were a public pretest.

                    /L/e/k/t/u

  reply	other threads:[~2006-11-27 20:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27  9:51 string-to-char martin rudalics
2006-11-27 10:52 ` string-to-char Juanma Barranquero
2006-11-27 19:32   ` string-to-char Nick Roberts
2006-11-27 20:13     ` Juanma Barranquero [this message]
2006-11-27 20:59       ` string-to-char Nick Roberts
2006-11-29  3:28       ` string-to-char Richard Stallman
2006-11-29  9:09         ` string-to-char Juanma Barranquero
2006-11-30  3:20           ` string-to-char Richard Stallman
2006-11-27 23:43   ` string-to-char Richard Stallman
2006-11-28  0:36   ` string-to-char Glenn Morris
2006-11-27 13:38 ` string-to-char Stefan Monnier

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=f7ccd24b0611271213w4faf1ca6wf42937d713e13fb8@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.