public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>
Subject: Re: `contrib/gcc_update --touch` and snapshots
Date: Wed, 23 Aug 2000 08:35:00 -0000	[thread overview]
Message-ID: <15810.967044846@upchuck> (raw)
In-Reply-To: <Pine.BSF.4.21.0008201819530.33859-100000@deneb.dbai.tuwien.ac.at>

  In message < Pine.BSF.4.21.0008201819530.33859-100000@deneb.dbai.tuwien.ac.at >
you write:
  > The real problem is that snapshots do not contain these generated files.
  > Didn't we agree to include these for FTP snapshots and releases?
Yes, but I simply don't have time to do it.  Yes, I should check the
snapshot script into CVS so that others can take care of it.  Egad, this is
going to be embarrassing.

jeff

      parent reply	other threads:[~2000-08-23  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-19 13:49 Gerald Pfeifer
2000-08-20  9:23 ` Gerald Pfeifer
2000-08-20 11:09   ` Mark Mitchell
2000-08-20 15:59     ` Bruce Korb
2000-08-23  8:35   ` Jeffrey A Law [this message]

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=15810.967044846@upchuck \
    --to=law@cygnus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).