unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: New assoc-let package
Date: Wed, 10 Dec 2014 14:00:44 -0500	[thread overview]
Message-ID: <87h9x372jn.fsf@lifelogs.com> (raw)
In-Reply-To: CAAdUY-KzKfWrRHug=E7JZYD_XjkB4hsPvgMRgbFYkt1Dp=EFTg@mail.gmail.com

On Wed, 10 Dec 2014 16:28:19 -0200 Artur Malabarba <bruce.connor.am@gmail.com> wrote: 

AM> 2014-12-10 15:49 GMT+00:00 Ted Zlatanov <tzz@lifelogs.com>:
>> On Wed, 10 Dec 2014 10:43:23 -0500 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> 
>>>> Hmm, I don't see that the Package header is necessary.  At least
>>>> cfengine.el doesn't have it.  Am I missing something?
>> 
SM> You're probably right.
>> 
>> All right, when Artur gives the final OK, I'll merge to master. He's in
>> the ChangeLog already so his contributor papers are OK.

AM> Thanks Ted, there's only one small thing I'd like to add at the end of
AM> the header comments (quoted below).
AM> I've added it as an ammend to your branch, and pushed it to the
AM> malabarba/let-alist-package-rc3 branch.

AM> ;; Note that only one level is supported.  If you nest `let-alist'
AM> ;; invocations, the inner one can't access the variables of the outer
AM> ;; one.

I added something similar but yours is better :)

;; Note that only one level is supported.  You can't nest `let-alist'
;; invocations safely.

AM> If you're ok with that feel free to merge.

Yup, except I cherry-picked to avoid the unnecessary merge message.
Feel free to delete your RC branch--I deleted mine.

Ted




  reply	other threads:[~2014-12-10 19:00 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 23:40 New assoc-let package Artur Malabarba
2014-12-04  3:54 ` Stefan Monnier
2014-12-05  0:36   ` Artur Malabarba
2014-12-05  2:49     ` Leo Liu
2014-12-06  2:27       ` Ted Zlatanov
2014-12-04 19:36 ` Ted Zlatanov
2014-12-05  0:33   ` Artur Malabarba
2014-12-05  0:45     ` Ted Zlatanov
2014-12-05 20:27       ` Artur Malabarba
2014-12-05 20:28         ` Artur Malabarba
2014-12-06 11:36           ` Christopher Schmidt
2014-12-06 19:24             ` Artur Malabarba
2014-12-06 19:58               ` Christopher Schmidt
2014-12-07 16:25                 ` Ted Zlatanov
2014-12-06  2:42         ` Ted Zlatanov
2014-12-06  4:55           ` Stefan Monnier
2014-12-08 10:56             ` Ted Zlatanov
2014-12-08 12:11               ` Artur Malabarba
2014-12-08 14:01                 ` Ted Zlatanov
2014-12-08 15:01                 ` Stefan Monnier
2014-12-08 14:59               ` Stefan Monnier
2014-12-08 15:35                 ` Ted Zlatanov
2014-12-08 15:56                 ` Stefan Monnier
2014-12-08 18:23                 ` Artur Malabarba
2014-12-08 18:28                   ` Artur Malabarba
2014-12-08 20:07                     ` Stefan Monnier
2014-12-09  3:37                       ` Artur Malabarba
2014-12-09 16:57                         ` Stefan Monnier
2014-12-10 15:20             ` Ted Zlatanov
2014-12-10 15:43               ` Stefan Monnier
2014-12-10 15:49                 ` Ted Zlatanov
2014-12-10 18:28                   ` Artur Malabarba
2014-12-10 19:00                     ` Ted Zlatanov [this message]
2014-12-10 19:09                   ` Stefan Monnier
2014-12-10 19:14                     ` Ted Zlatanov

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=87h9x372jn.fsf@lifelogs.com \
    --to=tzz@lifelogs.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 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).