public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Robert Lipe <robertl@dgii.com>
Cc: Oleg Krivosheev <kriol@FNAL.GOV>, egcs@cygnus.com
Subject: Re: Direct CVS Access to egcs sources
Date: Fri, 16 Jan 1998 02:26:00 -0000	[thread overview]
Message-ID: <20712.884940211@hurl.cygnus.com> (raw)
In-Reply-To: <19980115012422.08714@dgii.com>

  In message < 19980115012422.08714@dgii.com >you write:
  > Since not everyone will have CVS access, (much of the world is
  > still UUCP connected, for example) it's my understanding
  > that snapshots will still be made.  Even if everyone *did* have 
  > CVS access, not everyone will want to track things that closely.
Right.


  > We do need some way to distinguish the CVS snapshots of any given
  > moment in time.
Absolutely.

The question is how fine grained to we want to be able to distinguish
a checked out tree.  Daily?  Every check-in?  No decision has been
made, so further comments/suggestions are welcome.

  > Now people have a choice.   If they're CVS enabled (and internet 
  > connected) and can crank out an update/build/test each hour, they 
  > can find out *exactly* when something broke or began working.  (If 
  > you're actually in that category, perhaps getting outside once in a 
  > while would do you some good. :-)  If they're  not, they can wait for 
  > the announcement of the snaps and grab them as always.  Of course, 
  > if they are CVS enabled and just choose not to track the release of 
  > the moment, they can still use CVS to get to the snapshots via the
  > tags that are applied as part of the snapshot process.
Yup.

  > Having CVS access also allows us to work out patch integration 
  > issues in a way that we know they'll apply cleanly to the master
  > sources, making the lives of those with actual write access to the
  > master repository easier.
CVS access also makes is easier on those developing patches -- unless
there's a conflict with a change made in the repository CVS will
automatically merge in changes from the repository with your local changes.

If there's a conflict it will be clearly marked and you get to go fix
it :-)

[ More cool things about CVS removed... ]

  > We have lots of choices and options available to us now.   If you 
  > want to stay with the snapshot/patch model, I understand that'll 
  > still be available.
Absolutely.  The plan is to finish the last 10% of the snapshot script
so that it can run automatically at a preset time every week.  Unfortunately
I'll be on the road again most of next week, so it might be a couple weeks
before I sit down to finish things up.

jeff

  reply	other threads:[~1998-01-16  2:26 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
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               ` Bryan W. Headley
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-01-17 22:30       ` Raja R Harinath
1998-01-15 16:30   ` Robert Lipe
1998-01-16  2:26     ` Jeffrey A Law [this message]
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=20712.884940211@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=kriol@FNAL.GOV \
    --cc=robertl@dgii.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).