From: Joel Brobecker <brobecker@adacore.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Remove unknown.exp
Date: Tue, 15 May 2007 22:55:00 -0000 [thread overview]
Message-ID: <20070515225550.GC3559@adacore.com> (raw)
In-Reply-To: <200705152109.07166.vladimir@codesourcery.com>
Volodya,
> Per http://article.gmane.org/gmane.comp.gdb.devel/19790, I've committed
> the attached patch to remove testsuite/config/unknown.exp.
This is a tiny detail, but I think it would be better if the URL
you posted was refering to sourceware.org. It's pretty easy to find
a given message when you go to:
http://www.sourceware.org/ml/gdb-patches/
The idea is that we have some form of control of what goes in sourceware,
but I have not checked what gmane.org's policy is. I think it will make
safer later on if we need to do some archeology.
--
Joel
next prev parent reply other threads:[~2007-05-15 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 17:09 Vladimir Prus
2007-05-15 22:55 ` Joel Brobecker [this message]
2007-05-22 16:36 ` Vladimir Prus
2007-05-22 18:07 ` Joel Brobecker
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=20070515225550.GC3559@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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