From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: tar incremental backups and ctime problem
Date: Mon, 23 May 2016 19:02:00 -0000 [thread overview]
Message-ID: <574353B2.8010006@redhat.com> (raw)
In-Reply-To: <CAOKAGPO=h=J-MWYxN_wqSSGPvAJKP0ks7-hc+iQnUr4NZBiAuQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]
On 05/23/2016 10:56 AM, x y wrote:
>> It is always possible to create file list with find and use that
>> to tar whatever using --files-from=FILE option
>
>> I don't see the need to change tar behaviour to meet your wish.
>
> Hi Marco,
>
> Consider that you are working in the IT department of a company and
> you have thousands of documents in your file server. Concerning the
> --file-from option, how can you guess the name of the files which are
> just only going to be viewed by the workers? Those files would be not
> modified but since the ctime stamp will be updated, they will be
> included in the next incremental backup. Why to lose time with the
> --files-from option and make things more difficult? Adding an option
> to tar.exe to ignore the cname time stamp during differential \
> incremental backups should be possible. This should be the natural
> method. Tools like rsync does not suffer from such problems so my
> request should make sense.
If it makes that much sense, then propose the extension upstream
(bug-tar@gnu.org); once upstream implements it, Cygwin will pick it up
automatically. Until then, I don't see a reason for Cygwin to
needlessly differ from upstream.
>
> On Mon, May 23, 2016 at 6:35 PM, Marco Atzeri <marco.atzeri@gmail.com> wrote:
>> On 23/05/2016 16:57, x y wrote:
>>>>
>>>> mtime is fakeable, ctime is not. Using only mtime makes it likely that
You're still top-posting. It's okay to trim the portion of the email
you don't reply to.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-05-23 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 8:40 x y
2016-05-23 8:47 ` Marco Atzeri
2016-05-23 8:54 ` x y
2016-05-23 9:06 ` Marco Atzeri
2016-05-23 9:18 ` x y
2016-05-23 14:29 ` Eric Blake
2016-05-23 14:57 ` x y
2016-05-23 15:24 ` Vince Rice
2016-05-23 15:35 ` Marco Atzeri
2016-05-23 16:56 ` x y
2016-05-23 19:02 ` Eric Blake [this message]
2016-05-23 17:19 ` Erik Soderquist
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=574353B2.8010006@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).