From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Luke Lee <luke.yx.lee@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Please don't obsolete "crisp.el"
Date: Wed, 09 Jul 2014 09:24:18 -0400 [thread overview]
Message-ID: <jwvr41ur7mk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAA=xLRM4WHqyrRTohGwSF37bNsyUx8+6U6O6e7ARKqmY0e0Dxw@mail.gmail.com> (Luke Lee's message of "Wed, 9 Jul 2014 14:47:20 +0800")
> Basically I followed the steps described in StackOverflow, with some extra
> steps I successfully merging the full history of crisp.el *ONLY*. The
> original
> flow is discussed here: "http://stackoverflow.com/questions/1365541/
> how-to-move-files-from-one-git-repo-to-another-not-a-clone-preserving-history"
Which steps did you follow? The "git log | git am" ones or the "git
filter-branch" ones?
> Another drawback is that we might be confused since the history will
> contain both Emacs trunk commit messages and ELPA messages.
If it contains trunk commit messages unrelated to crisp.el, it sounds
like a serious problem, indeed.
Otherwise I don't understand why you think it's a problem. Can you show
some example?
Stefan
next prev parent reply other threads:[~2014-07-09 13:24 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 [this message]
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
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
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=jwvr41ur7mk.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 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).