From: Stefan Monnier <monnier@iro.umontreal.ca>
To: luke.yx.lee@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: Please don't obsolete "crisp.el"
Date: Mon, 21 Jul 2014 00:00:37 -0400 [thread overview]
Message-ID: <jwvbnsj9xe7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <ha2bxx9q.fsf@tw-fw-dt-1.i-did-not-set--mail-host-address--so-tickle-me> (luke yx lee's message of "Mon, 21 Jul 2014 10:26:25 +0800")
>> (1.4) Mangle the commit messages in crisp-history.patch to notify
>> these commits comes from Emacs repo.
Don't bother. We already imported many other packages with just "git
merge" and without mangling their commit messages.
>> Of course, before I did that we should have a proper message
>> prefix/postfix the commit messages from Emacs trunk, to prevent
>> confusing ELPA existing commit log (i.e. the above skipped step 1.4).
There's no confusion: those commits are on a branch and Git knows it.
"git log" tends to display them along with everything else, but it's
a problem with the default "git log" behavior (which can be fixed with
appropriate options, IIUC), not with the history data.
Other than that it looks OK, thank you.
Stefan
next prev parent reply other threads:[~2014-07-21 4:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 9:13 Please don't obsolete "crisp.el" Luke Lee
2014-07-07 15:58 ` Glenn Morris
2014-07-07 16:36 ` Stefan Monnier
2014-07-08 5:01 ` Luke Lee
2014-07-08 18:42 ` Glenn Morris
2014-07-08 20:04 ` Stefan Monnier
2014-07-09 6:47 ` Luke Lee
2014-07-09 10:39 ` Luke Lee
2014-07-09 13:24 ` Stefan Monnier
2014-07-10 2:43 ` Luke Lee
2014-07-10 6:20 ` Luke Lee
2014-07-10 13:48 ` Stefan Monnier
2014-07-10 14:26 ` Stefan Monnier
2014-07-11 10:03 ` Luke Lee
2014-07-11 10:32 ` Yuri Khan
2014-07-14 10:28 ` Luke Lee
2014-07-11 12:44 ` Andreas Schwab
2014-07-14 10:30 ` Luke Lee
2014-07-11 13:32 ` Stefan Monnier
2014-07-14 10:29 ` Luke Lee
2014-07-21 2:26 ` luke.yx.lee
2014-07-21 4:00 ` Stefan Monnier [this message]
2014-07-12 14:47 ` Stephen Leake
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=jwvbnsj9xe7.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=luke.yx.lee@gmail.com \
/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.