public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ken Raeburn <raeburn@cygnus.com>
To: eric@tantalus.nrl.navy.mil (Eric Youngdale)
Cc: gas2@cygnus.com
Subject: Re: Snapshots broken again??
Date: Mon, 11 Jul 1994 11:57:00 -0000	[thread overview]
Message-ID: <199407111857.OAA20617@cujo.cygnus.com> (raw)
In-Reply-To: <9407111625.AA24736@tantalus.nrl.navy.mil>

   Date: Mon, 11 Jul 94 12:25:31 EDT
   From: eric@tantalus.nrl.navy.mil (Eric Youngdale)


	   The two latest sets of daily diffs between the snapshots were only 20
   bytes - large enough for a compressed zero length file.  It would appear that
   some changes did indeed occur if you look at the sizes of the full
   distributions.

   -Eric

Yup.  The usual deal, you "fix" a bug then disappear for the weekend...
The snapshot script is a bit of a pain to debug; I'd planned on checking
its progress on Saturday after letting it run automatically one night.

I'm not sure what caused the zero-length *daily* diffs, but I fixed a
bug in some revised handling the weekly diffs, and my test run seems to
have generated both daily and weekly diffs okay.  I re-did today's
snapshot as part of the test, and I've manually build diffs from the
940709 snapshot.

The original changes to the weekly diffs were intended to avoid the
multi-week gap between them if the script failed to run to completion on
Tuesday, the one night they were getting made.  Now it ought to decide
based on the age, with a preference for Tuesday night.


           reply	other threads:[~1994-07-11 11:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <9407111625.AA24736@tantalus.nrl.navy.mil>]

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=199407111857.OAA20617@cujo.cygnus.com \
    --to=raeburn@cygnus.com \
    --cc=eric@tantalus.nrl.navy.mil \
    --cc=gas2@cygnus.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).