From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] Config in VCS
Date: Sat, 28 Mar 2009 11:03:40 +0100 [thread overview]
Message-ID: <1238234052-sup-2032@ausone.home> (raw)
In-Reply-To: <49CD0B3E.9010002@cs.rpi.edu>
Excerpts from Ethan Glasser-Camp's message of Fri Mar 27 18:22:06 +0100 2009:
> Hi, long time reader, first time caller.
>
> Many years ago I used fetchmail+Mutt to handle my mail, but all my
> configuration was lost in a hard drive crash and I didn't have the
> energy to recreate it. So as I look at sup, I am judging how difficult
> it is to keep its configuration in a git repo (for easier replication
> and backup).
>
> One problem I see is that sources.yaml contains both all the information
> about how to access a source, and its current state. I would like to
> keep the first in version control, and the second not. So I would like
> sources.yaml split into a sources.yaml and a sources-state.yaml; the
> first one would be the information about how to access the sources, and
> the second one would map source ID to its cur_offset.
I keep my sup configuration including the whole sources.yaml file in a
darcs repository. Even if the data was split in two files I would prefer
to also save it.
About backups, I recommend sup users to make regular sup-dump's, not only
because sup still have bugs but also because it's the only (meta)data
needed to reconstruct your index.
**NOTE to sup developers**
Moreover I think that sup should write a log file being some kind of sup-dump
delta:
messageid (oldlabel1 oldlabel2 -> oldlabel2 newlabel3)
...
I think I will try to implement this feature soon.
--
Nicolas Pouillard
next prev parent reply other threads:[~2009-03-28 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 17:22 Ethan Glasser-Camp
2009-03-28 10:03 ` Nicolas Pouillard [this message]
2009-03-31 4:57 ` Ethan Glasser-Camp
2009-03-31 11:39 ` Nicolas Pouillard
2009-03-31 13:36 ` Ben Walton
2009-04-01 8:41 ` David Guibert
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=1238234052-sup-2032@ausone.home \
--to=nicolas.pouillard@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox