From: Marc Espie <Marc.Espie@liafa.jussieu.fr>
To: Richard Henderson <rth@cygnus.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: newbie question
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990513190153.A25983@liafa1.liafa.jussieu.fr> (raw)
In-Reply-To: <19990513095557.B28238@cygnus.com>
On Thu, May 13, 1999 at 09:55:57AM -0700, Richard Henderson wrote:
> > - are snapshots still alive?
> Not as such, but they could be revived.
Depends on how much hastle it is for you...
From my perspective, I don't test everything everywhere. I send out
patches to fellow developpers who try them out, tell me what's wrong,
and then I get all the fun of finding out what went wrong on their arch...
and plaguing them to send copyright assignments if their changes are large
enough :)
My setup is getting better for this, as I now have mostly functional
cross-toolchains :)
Problem is that, before importing new stuff, I have to send out patches
+ check points out. Some of them don't have fast net access, so a snapshot
is easier than cvs.
If I'm the only one concerned, I can still get cvs source out and brew my
own `snapshots' in a corner, but, assuming I'm not the only one who works that
way, `generic' snapshots would make sense.
--
Marc Espie
|anime, sf, juggling, unicycle, acrobatics, comics...
|AmigaOS, OpenBSD, C++, perl, Icon, PostScript...
| `real programmers don't die, they just get out of beta'
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Marc Espie
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Marc Espie [this message]
1999-07-01 0:00 ` Andreas Schwab
1999-07-01 0:00 ` joel
2002-05-16 9:14 Newbie Question Jeffrey Stephens
2002-05-16 17:58 ` Alan Modra
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=19990513190153.A25983@liafa1.liafa.jussieu.fr \
--to=marc.espie@liafa.jussieu.fr \
--cc=binutils@sourceware.cygnus.com \
--cc=rth@cygnus.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).