unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: lexbind ready for merge
Date: Wed, 30 Mar 2011 07:30:53 -0400	[thread overview]
Message-ID: <E1Q4tbx-0007Uu-W4@fencepost.gnu.org> (raw)
In-Reply-To: <877hbhxe12.fsf@member.fsf.org> (message from Tassilo Horn on Wed, 30 Mar 2011 09:28:57 +0200)

> From: Tassilo Horn <tassilo@member.fsf.org>
> Date: Wed, 30 Mar 2011 09:28:57 +0200
> Cc: emacs-devel@gnu.org
> 
> Please go for it.
> [...]
> ...except that the current git version of Gnus doesn't build with
> lexbind emacs:

So how is it a good idea to "go for it"?  Gnus is resync'ed with Emacs
practically every day, so chances are they will resync before Stefan
gets around to merging the branch.



  reply	other threads:[~2011-03-30 11:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 21:44 lexbind ready for merge Stefan Monnier
2011-03-29 23:43 ` Daniel Colascione
2011-03-30  1:22   ` Stefan Monnier
2011-03-30  4:10     ` Daniel Colascione
2011-03-30 11:35       ` Juanma Barranquero
2011-03-30 13:24         ` lexbind: how to replace lexical-let approach to hide secrets (was: lexbind ready for merge) Ted Zlatanov
2011-03-30 21:12           ` lexbind: how to replace lexical-let approach to hide secrets Stefan Monnier
2011-03-30 21:56             ` David Kastrup
2011-03-30 22:29               ` Daniel Colascione
2011-03-31 15:42             ` Ted Zlatanov
2011-04-01  1:31               ` Stephen J. Turnbull
2011-04-01  4:41                 ` secret strings (was: lexbind: how to replace lexical-let approach to hide secrets) Ted Zlatanov
2011-04-01  5:52                   ` Stephen J. Turnbull
2011-04-01 11:02                     ` secret strings Ted Zlatanov
2011-04-01 14:38                       ` Stephen J. Turnbull
2011-04-01 15:12                         ` Ted Zlatanov
2011-04-01 16:14                           ` Stephen J. Turnbull
2011-04-01 20:08                             ` Ted Zlatanov
2011-04-01 20:34                               ` Stefan Monnier
2011-04-01 21:25                                 ` Ted Zlatanov
2011-04-01 14:59                       ` Stefan Monnier
2011-03-30 15:09         ` lexbind ready for merge Daniel Colascione
2011-03-30 15:20           ` Juanma Barranquero
2011-03-30 14:26       ` Stefan Monnier
2011-03-30  7:28 ` Tassilo Horn
2011-03-30 11:30   ` Eli Zaretskii [this message]
2011-03-30 13:10     ` Tassilo Horn
2011-03-30 13:17     ` Ted Zlatanov
2011-03-30 14:29   ` Stefan Monnier
2011-03-30 14:54     ` Tassilo Horn
2011-03-31  1:02       ` Stephen J. Turnbull
2011-03-30 16:11     ` Lars Magne Ingebrigtsen
2011-03-30 17:10       ` Tassilo Horn

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Q4tbx-0007Uu-W4@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=tassilo@member.fsf.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 public inbox

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

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).