public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: H.J. Lu <hjl@lucon.org>
To: egcs@cygnus.com
Subject: Re: A patch for configure.in
Date: Tue, 19 Aug 1997 01:10:45 -0000	[thread overview]
Message-ID: <m0x0cpy-0004edC@ocean.lucon.org> (raw)
In-Reply-To: 5750.871853861@hurl.cygnus.com

> 
>   In message <m0x08nj-0004ecC@ocean.lucon.org>you write:
>   > Can we use this patch? I'd like to keep the binaries for all versions
>   > if my disk space allows.
> How about we just bump the last # in the version for each snapshot?
> 
> Jeff
> 

I prefer date since it is easy to track. But I don't really mind
either way.

-- 
H.J. Lu (hjl@gnu.ai.mit.edu)

             reply	other threads:[~1997-08-19  1:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-19  1:10 H.J. Lu [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-08-17 21:48 An autoconf patch H.J. Lu
1997-08-17 21:48 ` A patch for configure.in Jeffrey A Law
1997-08-17 16:44 H.J. Lu

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=m0x0cpy-0004edC@ocean.lucon.org \
    --to=hjl@lucon.org \
    --cc=egcs@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).