From: Mathieu Lirzin <mthl@gnu.org>
To: Catonano <catonano@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH 0/4]
Date: Sun, 29 May 2016 14:20:14 +0200 [thread overview]
Message-ID: <87eg8lrr7l.fsf@gnu.org> (raw)
In-Reply-To: <CAJ98PDxbBmoJ6Rp8HeRJLeGwbRAMFKQ3kK-t5tn2aL3=YejpbA@mail.gmail.com> (catonano@gmail.com's message of "Sun, 29 May 2016 13:59:08 +0200")
Catonano <catonano@gmail.com> writes:
> This is a bunch of emacs packages I made on the same branch, so git
> shouldn't claim any inconsistency with these.
>
> I hope this attempt is gonna be successful
>
> they are
>
> 1) emacs.queue
> 2) emacs-pkg-info
> 3) emacs-spinner
> 4) emacs-seq
Please make an effort to send these patches to the appropriate mailing
list.
Thanks.
--
Mathieu Lirzin
next prev parent reply other threads:[~2016-05-29 12:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 11:59 [PATCH 0/4] Catonano
2016-05-29 12:00 ` Catonano
2016-05-29 12:01 ` Catonano
2016-05-29 12:01 ` Catonano
2016-05-29 12:02 ` Catonano
2016-05-29 12:20 ` Mathieu Lirzin [this message]
2016-05-29 13:12 ` Catonano
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eg8lrr7l.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=catonano@gmail.com \
--cc=guile-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.
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).