From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Gnus registry upgrade didn't import old registry
Date: Mon, 26 Sep 2011 15:25:54 -0500 [thread overview]
Message-ID: <87litbxd7x.fsf@lifelogs.com> (raw)
In-Reply-To: <87ehzkh4j2.fsf@uwo.ca>
On Tue, 13 Sep 2011 10:59:29 -0400 Dan Christensen <jdc@uwo.ca> wrote:
DC> When I started a recent Gnus, it created a new registry, but didn't
DC> slurp in my old registry. Was it supposed to?
Sorry for the inconvenience. You have to use `gnus-registry-import-eld'
but it's not called automatically. The reason is that it doesn't remove
the old file so it could get imported twice. I'm not sure how to best
deal with this issue...
The good news is, importing won't wipe your current registry. But
please back up beforehand anyway.
Ted
next prev parent reply other threads:[~2011-09-26 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 14:59 Dan Christensen
2011-09-26 20:25 ` Ted Zlatanov [this message]
2011-09-26 20:37 ` Dan Christensen
2011-09-26 20:50 ` Dan Christensen
2011-09-26 22:02 ` Ted Zlatanov
2011-09-27 2:12 ` Dan Christensen
2011-09-27 2:35 ` Dan Christensen
2011-09-27 21:25 ` Ted Zlatanov
2011-09-28 2:43 ` Dan Christensen
2011-09-29 0:37 ` Ted Zlatanov
2011-09-27 10:42 ` Ted Zlatanov
2011-09-26 20:41 ` Dan Christensen
2011-09-26 21:57 ` Ted Zlatanov
2011-09-27 2:07 ` Dan Christensen
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=87litbxd7x.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).