From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: ELPA queue.el weirdness
Date: Thu, 15 May 2014 09:36:32 +0200 [thread overview]
Message-ID: <87ha4rtrwf.fsf@zigzag.favinet> (raw)
In-Reply-To: <jwvmwektc51.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 14 May 2014 15:05:08 -0400")
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
() Stefan Monnier <monnier@IRO.UMontreal.CA>
() Wed, 14 May 2014 15:05:08 -0400
You could "git merge -t subtree" from that repository.
Thanks for the tip (with ‘s/-t/-s/’ i take it).
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2014-05-15 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 18:25 ELPA queue.el weirdness Thien-Thi Nguyen
2014-05-14 19:05 ` Stefan Monnier
2014-05-15 7:36 ` Thien-Thi Nguyen [this message]
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=87ha4rtrwf.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--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).