From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: New tar available for testing (was Re: here is a patch for gnu tar incremental backup...)
Date: Mon, 10 Nov 2003 14:25:00 -0000 [thread overview]
Message-ID: <20031110142535.GA13408@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0311101254410.7007@dipsy.eng.gla.ac.uk>
On Mon, Nov 10, 2003 at 01:25:02PM +0000, Jeremy Green wrote:
>I.e. files/foo/bar is backed-up even though it hasn't changed. With the
>application of the following patch to the tar-1.13.25-4 source package:
>
>--- src/incremen.c.orig 2003-11-10 12:27:36.094206400 +0000
>+++ src/incremen.c 2003-11-10 12:33:06.629492800 +0000
>@@ -437,7 +437,7 @@ read_directory_file (void)
>
> errno = 0;
> #ifdef __CYGWIN_USE_BIG_TYPES__
>- ino = strtoul (strp, &ebuf, 10);
>+ ino = strtoull (strp, &ebuf, 10);
> #else
> ino = strtoul (strp, &ebuf, 10);
> #endif
Odd. I already have that change in my sandbox already but I must have
made the change after uploading the file. I'll refresh the source and
binaries shortly.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-11-10 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 13:21 Jeremy Green
2003-11-10 14:25 ` Christopher Faylor [this message]
2003-11-10 17:47 ` Available for testing: tar-1.13.25-5 Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2003-10-27 17:06 here is a patch for gnu tar incremental backup (-g) or (--listed-incremental) George Carrette
2003-11-08 21:04 ` New tar available for testing (was Re: here is a patch for gnu tar incremental backup...) Christopher Faylor
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=20031110142535.GA13408@redhat.com \
--to=cgf-no-personal-reply-please@cygwin.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).