From: glasse@cs.rpi.edu (Ethan Glasser-Camp)
Subject: [sup-talk] Config in VCS
Date: Tue, 31 Mar 2009 00:57:38 -0400 [thread overview]
Message-ID: <49D1A2C2.4020406@cs.rpi.edu> (raw)
In-Reply-To: <1238234052-sup-2032@ausone.home>
Nicolas Pouillard wrote:
> 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.
Really? How often do you commit? Certainly not every mail message..
Aren't you uncomfortable with your working copy becoming dirty every
time you receive mail?
Ethan
next prev parent reply other threads:[~2009-03-31 4:57 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
2009-03-31 4:57 ` Ethan Glasser-Camp [this message]
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=49D1A2C2.4020406@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