From: Jeffrey A Law <law@cygnus.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: kriol@fnal.gov, egcs@cygnus.com
Subject: Re: Direct CVS Access to egcs sources
Date: Sun, 08 Feb 1998 00:29:00 -0000 [thread overview]
Message-ID: <10721.886926687@hurl.cygnus.com> (raw)
In-Reply-To: <199801151801.KAA03652@atrus.synopsys.com>
In message <199801151801.KAA03652@atrus.synopsys.com>you write:
> I think that it will have a huge advantage. Let's say two people send in
> test reports for the same platform, with the same version, and one has an
> additional failure. With cron-generated timestamps, you'll have to search
> through a whole day's changes to figure out if some patch caused the
> failure. With an update-on-every-checkin version, you know they are
> running identical code and you can start looking for subtle system
> differences.
>
> You could lessen the problem by doing a new version string every hour,
> say, but then people may have identical software that differs only in
>
> a version number.
How about we continue to bump the version # for snapshots, but change
the "date" string via a nightly cron job?
I just don't see the need at this point to bump the version # at each
checkin -- that (of course) can change if we have a difficult time
interpreting test results.
Does this sound reasonable?
jeff
next prev parent reply other threads:[~1998-02-08 0:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-13 4:52 Jeffrey A Law
1998-01-14 8:18 ` Oleg Krivosheev
1998-01-14 8:42 ` Jeffrey A Law
1998-01-15 16:06 ` Joe Buck
1998-01-15 16:30 ` Jeffrey A Law
1998-01-16 1:51 ` Joe Buck
1998-02-08 0:29 ` Jeffrey A Law [this message]
1998-02-08 7:13 ` Gerald Pfeifer
1998-02-08 8:57 ` Dave Love
1998-02-08 10:14 ` Jeffrey A Law
1998-02-08 13:23 ` H.J. Lu
1998-02-08 15:38 ` Jeffrey A Law
1998-02-08 15:20 ` H.J. Lu
1998-02-08 15:38 ` Jeffrey A Law
1998-02-08 18:35 ` Todd Vierling
1998-02-08 15:38 ` Bryan W. Headley
1998-01-17 22:30 ` Raja R Harinath
1998-01-15 16:30 ` Robert Lipe
1998-01-16 2:26 ` Jeffrey A Law
1998-01-15 16:30 ` Franz Sirl
1998-01-17 1:40 ` Robert Lipe
1998-01-17 22:30 ` Joseph H. Buehler
1998-01-19 2:25 ` Robert Lipe
1998-01-19 2:30 ` Fred Fish
1998-01-19 2:30 ` Jeffrey A Law
1998-01-20 4:00 Mike Stump
[not found] <199801142227.OAA03715@cygnus.com>
1998-01-23 0:20 ` Jeffrey A Law
1998-01-23 11:15 ` Franz Sirl
[not found] <199801231742.JAA01350@cygnus.com>
1998-01-23 9:47 ` Jeffrey A Law
[not found] <19980209020929.50632@cerebro.laendle>
1998-02-08 22:42 ` Jeffrey A Law
1998-02-09 19:49 ` Joern Rennecke
1998-02-09 21:34 ` Jeffrey A Law
1998-02-11 10:25 ` Marc Lehmann
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=10721.886926687@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.com \
--cc=kriol@fnal.gov \
/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).