From: wagnerdm@seas.upenn.edu (wagnerdm at seas.upenn.edu)
Subject: [sup-talk] Backups ?
Date: Tue, 07 Jul 2009 11:26:35 -0400 [thread overview]
Message-ID: <20090707112635.14736pk1mxi8r9k4@webmail.seas.upenn.edu> (raw)
In-Reply-To: <20090707130844.GA23073@gmx.de>
Quoting Marc Weber <marco-oweber at gmx.de>:
> ls -1t "$dump_dir"/sup-dumps-* | { read; read; read; read; cat } | xargs rm
"{ read; read; read; read; cat }" could probably better be done as
"tail +5"; makes it easier to adjust to people's choice of backup
count, too. ;-)
- Daniel "Bikeshedder" Wagner
next prev parent reply other threads:[~2009-07-07 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 13:08 Marc Weber
2009-07-07 15:26 ` wagnerdm at seas.upenn.edu [this message]
2009-07-07 16:10 ` Ben Walton
2009-07-07 16:19 ` Ingmar Vanhassel
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=20090707112635.14736pk1mxi8r9k4@webmail.seas.upenn.edu \
--to=wagnerdm@seas.upenn.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