public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ranjit Mathew <rmathew@hotmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc@gcc.gnu.org
Subject: Re: 3.5 Snapshots (Again)
Date: Tue, 09 Mar 2004 06:51:00 -0000	[thread overview]
Message-ID: <404D693C.1060503@hotmail.com> (raw)
In-Reply-To: <Pine.BSF.4.58.0403082031140.82762@acrux.dbai.tuwien.ac.at>

Gerald Pfeifer wrote:
>>The last time this issue was raised by Kelly Cook nothing happened, so
>>I'm raising this yet again: can we please start having 3.5 snapshots?
> 
> 
> First we need some infrastructure changes to get the diffs right,
> that's the major blocker right now.

If you mean the diffs from the last 3.4 snapshot
to the newly generated 3.5 snapshot so that
people with current snapshots can transition
easily, yes I agree. But then, I think these diffs
are going to be pretty big anyway and it might be
better to avoid them altogether and just download
the whole snapshot once more (and continue
with diffs in subsequent weeks).


> I'll try to work on that tonight.

Thank you.


>>The policy should be to publish snapshots from the current development
>>tree (mainline) and the current release tree - as I said before, I don't
>>think there are hordes of hackers just waiting for their weekly 3.3
>>snapshots at this point.
> 
> 
> Snapshots are not just used by hacker, but also by the FreeBSD system
> and probably other as well.  And there are quite few hackers which do
> not have CVS access.  In fact, it is hardly possible to contribute code
> to GCC with only snapshot access, as one cannot do proper testing.

I didn't know about the FreeBSD part...

I am one of those hackers who do not have CVS access,
mainly because of bandwidth problems (dial-up is quite
unreliable here and "broadband" is expensive and
unnecessarily restrictive).

I tend to test and submit patches, if any, close
to the release of the snapshots to avoid being too
out of sync with CVS. In any case, my changes are
mostly to GCJ which doesn't violently change every
week. :-)

Ranjit.

-- 
Ranjit Mathew          Email: rmathew AT hotmail DOT com

Bangalore, INDIA.      Web: http://ranjitmathew.tripod.com/

  reply	other threads:[~2004-03-09  6:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08 10:24 Ranjit Mathew
2004-03-08 19:34 ` Gerald Pfeifer
2004-03-09  6:51   ` Ranjit Mathew [this message]
2004-03-14  1:56     ` Gerald Pfeifer

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=404D693C.1060503@hotmail.com \
    --to=rmathew@hotmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.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).