From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: missing quote in define-package arg
Date: Sun, 25 May 2014 19:05:24 +0200 [thread overview]
Message-ID: <87oaylwzzf.fsf@zigzag.favinet> (raw)
In-Reply-To: <87mwe7grv5.fsf@zigzag.favinet> (Thien-Thi Nguyen's message of "Sat, 24 May 2014 16:42:54 +0200")
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
() Thien-Thi Nguyen <ttn@gnu.org>
() Sat, 24 May 2014 16:42:54 +0200
I am presently reading the BzrForEmacsDevs page on the EmacsWiki
(while waiting for bzr-initiated bits to percolate my way through the
net), and hope to install a fix, as well as the simplification you
suggest, shortly.
Both fix and optimization (rather, cruft avoidance) are now installed,
presuming i haven't screwed up somehow[0] -- it seems to work fine w/
ascii-art-to-unicode.el, at least. Onwards, slug!
_____________________________________________
[0] Being used to Git, i'm a little nervous w/ the "bound branch"
approach, but that's what's recommended on EmacsWiki. Ideally,
there is a Bazaar analog to the workflow where i can do a series
of commits w/o worrying too much about form (ChangeLog, primarily)
followed by a squash and "serious" commit, followed by a push.
It seems the bound branch approach makes *every* commit serious.
--
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: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-05-25 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 7:18 missing quote in define-package arg Thien-Thi Nguyen
2014-05-24 8:02 ` Thien-Thi Nguyen
2014-05-24 11:32 ` Dmitry Gutov
2014-05-24 14:42 ` Thien-Thi Nguyen
2014-05-24 19:57 ` Dmitry Gutov
2014-05-25 7:53 ` Thien-Thi Nguyen
2014-05-25 17:05 ` Thien-Thi Nguyen [this message]
2014-05-26 0:19 ` Stephen J. Turnbull
2014-05-26 9:15 ` Thien-Thi Nguyen
2014-05-27 19:23 ` chad
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=87oaylwzzf.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 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.