From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Request inclusion of ioccur.el in ELPA
Date: Wed, 14 Mar 2012 18:25:52 +0100 [thread overview]
Message-ID: <87aa3jnlgf.fsf@gmail.com> (raw)
In-Reply-To: <jwvbonzwdp3.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 14 Mar 2012 08:53:05 -0400")
Hi Stefan,
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Ok, better waiting you fix this, take your time, no urgency!
>
> OK, it looks like the repository is not really corrupted: you can still
> check it out, just not directly.
Good news.
> I.e. you have to "bzr checkout -r 170 ...elpa" and then "bzr update".
> So, it can probably be fixed by fixin bzr without changing the
> repository. So I installed your ioccur, with the patch below.
Thank you very much.
> It has full history, AFAIK, but I have no experience with bzr-hg, so
> I don't know how future merges may or may not work.
Ok, I will check if you use the very last changes
(i.e "hg update -C development")
> IOW, if you can use the emacs/elpa as the upstream from now on, that's
> better.
Yes I will do that.
Thanks also for the patch.
--
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2012-03-14 17:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 9:15 Request inclusion of ioccur.el in ELPA Thierry Volpiatto
2012-01-24 17:59 ` Stefan Monnier
2012-01-24 19:03 ` Thierry Volpiatto
2012-03-14 12:53 ` Stefan Monnier
2012-03-14 17:25 ` Thierry Volpiatto [this message]
2012-03-15 8:25 ` Chong Yidong
2012-03-15 9:23 ` Andreas Schwab
2012-03-16 1:11 ` Stefan Monnier
2012-03-23 16:17 ` Thierry Volpiatto
2012-03-23 17:41 ` Stefan Monnier
2012-03-23 19:17 ` Thierry Volpiatto
2012-03-24 13:49 ` Chong Yidong
2012-03-24 14:49 ` Thierry Volpiatto
2012-02-20 13:29 ` Thierry Volpiatto
2012-02-20 17:26 ` Stefan Monnier
2012-02-20 22:36 ` Thierry Volpiatto
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=87aa3jnlgf.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.