Re: Direct CVS Access to egcs sources

[Jeffrey A Law <law@cygnus.com>]

  In message < m0y1g1b-0004ecC@ocean.lucon.org >you write:
  > >   > 
  > >   > Can we bump the version # if there is any change as well as
  > >   > the "date" string everyday? It can be done via a nightly cron job.
  > > That just seems like overkill at this time.  It's not clear that we
  > > need the version # to change every time.
  > > 
  > > And the cost of doing that is noticable -- we would have had over 700
  > 
  > When did egcs start? If one version is generated per day, it
  > should be less than 700. If there is any change made to egcs/gcc,
  > egcs-2.x.y 98mmdd is updated to egcs-2.x.y+1 98mmdd.
Sorry, I mis-understood, I thought you meant on each checkin.

  > > versions by now, and each and every one that you built and installed
  > > would have gone into its own install directory.
  > 
  > That is what I want. I can easily remove those. But I may not
  > want to override the previous one. It helps track down the new
  > bug when it appears.
But it's not clear if that's what the rest of the folks here want; we've
had a couple for and a couple against.

How about this -- we'll ask folks to vote.  I'm willing to abide by
whatever decision the group makes on this subject.

Say we close the voting on Feb 28th?

Options:


  a. Version # updated for every checkin, date in version string updated
  nightly.

  b. Version # and date in version string updated nightly.

  c. Version # updated for snaphots, date in version string updated nightly

  d. Version # and date updated for snapshots

  e. Write in candidates.


Anyone want to tabulate votes?  Basically keep track of who voted and what
selection they voted for.  If nobody else wants to, I'll do it (or better
yet, someone want to dontate web expertise to have it do these things for
us?

jeff




  


  > 
  > 
  > 
  > -- 
  > H.J. Lu (hjl@gnu.org)