From: Ian Lance Taylor <ian@airs.com>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: overseers@sourceware.org
Subject: Re: [Fwd: Re: README.ADDING.NEW.BOARDS]
Date: Tue, 15 Jun 2004 20:40:00 -0000 [thread overview]
Message-ID: <m3oenko9ts.fsf@gossamer.airs.com> (raw)
In-Reply-To: <40CF58B9.6000601@eCosCentric.com>
Jonathan Larmour <jifl@eCosCentric.com> writes:
> Can someone remind me of the exact rune to use to stop these broken
> pipes? There was some change to CVSROOT/loginfo IIRC. I tried to fix
> this before based on what I thought was recommended here before, but
> my fix broke things, so perhaps I misinterpreted something. So can
> someone give me something that definitely works?
Here is my (unapproved) for the same problem in gcc:
http://gcc.gnu.org/ml/gcc-patches/2004-06/msg00699.html
Ian
next prev parent reply other threads:[~2004-06-15 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 20:27 Jonathan Larmour
2004-06-15 20:40 ` Ian Lance Taylor [this message]
2004-06-16 12:22 ` Gerald Pfeifer
2004-06-16 16:14 ` Ian Lance Taylor
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=m3oenko9ts.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=jifl@eCosCentric.com \
--cc=overseers@sourceware.org \
/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).