public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: egcs@cygnus.com
Subject: Re: Inconsistance in snapshots repository
Date: Tue, 14 Apr 1998 21:01:00 -0000	[thread overview]
Message-ID: <orpviju78e.fsf@zecarneiro.lsd.dcc.unicamp.br> (raw)
In-Reply-To: <Pine.GSO.3.96.980415001559.3746A-100000@alcyone.dbai.tuwien.ac.at>

Gerald Pfeifer writes:

> And on a final related note, I suggest to use 19980404 instead of 980404,
> unless egcs won't be Y2000-compliant! <g>

BTW, would it be possible to have a ``moving tag'' called
`egcs_latest_snapshot', updated whenever a snapshot is released?

With this, I would be able to simply `cvs update' my CVS tree, instead 
of having to `cvs update -r egcs_ss_<snapshot>'.  This has got harder
over time, since snapshots are released with dates from 2-3 days ago,
and I was bitten by a mistyped date more than once already.  Jeff?

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil


  reply	other threads:[~1998-04-14 21:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-14  9:37 Gabriel Dos Reis
1998-04-14 13:21 ` Jeffrey A Law
1998-04-14 15:23 ` Gerald Pfeifer
1998-04-14 21:01   ` Alexandre Oliva [this message]
1998-04-15 15:09     ` Jeffrey A Law
1998-04-15 23:03       ` Raja R Harinath
1998-04-16 10:35         ` Jeffrey A Law
1998-04-16 23:59       ` Craig Burley
1998-04-16 23:59         ` Jeffrey A Law
1998-04-17 14:42           ` Joe Buck
1998-04-17 23:53             ` Jeffrey A Law
1998-04-16 23:59         ` Alexandre Oliva
1998-04-16 18:39           ` Craig Burley
1998-04-16 18:39             ` Jeffrey A Law
1998-04-14 23:16   ` Jeffrey A Law
1998-04-23 13:31     ` Gerald Pfeifer
1998-05-24  2:32       ` Jeffrey A Law

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=orpviju78e.fsf@zecarneiro.lsd.dcc.unicamp.br \
    --to=oliva@dcc.unicamp.br \
    --cc=egcs@cygnus.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).