From: glasse@cs.rpi.edu (Ethan Glasser-Camp)
Subject: [sup-talk] Config in VCS
Date: Fri, 27 Mar 2009 13:22:06 -0400 [thread overview]
Message-ID: <49CD0B3E.9010002@cs.rpi.edu> (raw)
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.
What do you think?
Ethan
next reply other threads:[~2009-03-27 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 17:22 Ethan Glasser-Camp [this message]
2009-03-28 10:03 ` Nicolas Pouillard
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=49CD0B3E.9010002@cs.rpi.edu \
--to=glasse@cs.rpi.edu \
/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