From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] Config in VCS
Date: Tue, 31 Mar 2009 13:39:16 +0200 [thread overview]
Message-ID: <1238499402-sup-7426@ausone.inria.fr> (raw)
In-Reply-To: <49D1A2C2.4020406@cs.rpi.edu>
Excerpts from Ethan Glasser-Camp's message of Tue Mar 31 06:57:38 +0200 2009:
> 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?
I commit when I make a change to the configuration, add a contact, change
a hook, or add a label. So yes essentially my working copy always have
unrecorded changes, and I do not consider this harmful.
--
Nicolas Pouillard
next prev parent reply other threads:[~2009-03-31 11:39 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
2009-03-31 11:39 ` Nicolas Pouillard [this message]
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=1238499402-sup-7426@ausone.inria.fr \
--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