From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Acme, dump, and $HOME
Date: Mon, 13 Jan 2014 14:19:20 -0500 [thread overview]
Message-ID: <68a0b807567ccd21c51d85db24fe74a5@coraid.com> (raw)
In-Reply-To: <CAOw7k5jyekz+vGM4SmvB2QyiHn2cmcvEuj8iVwUb-8ECbCeqBQ@mail.gmail.com>
>
> The idea is that the dump file is a snapshot of a particular state, and it
> made sense to me to update
> the given state, instead of putting it back in the default file despite
> being given an explicit state.
> That seemed to me a bit contrary.
also if a snapshot is wanted, then we have a tool for that: cp(1). :-)
- erik
next prev parent reply other threads:[~2014-01-13 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 16:42 Paul Lalonde
2014-01-13 16:49 ` dexen deVries
2014-01-13 18:29 ` Paul Lalonde
2014-01-13 16:57 ` Charles Forsyth
2014-01-13 18:30 ` Paul Lalonde
2014-01-13 18:53 ` Bence Fábián
2014-01-13 19:01 ` Paul Lalonde
2014-01-13 19:17 ` Charles Forsyth
2014-01-13 19:18 ` erik quanstrom
2014-01-13 19:19 ` erik quanstrom [this message]
2014-01-13 19:36 ` Paul Lalonde
2014-01-13 21:39 ` Pete
2014-01-16 5:39 ` b.
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=68a0b807567ccd21c51d85db24fe74a5@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
/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).