From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Denis PILAT <denis.pilat@st.com>
Cc: insight@sources.redhat.com
Subject: Re: testsuite/gdb.gdbtk
Date: Wed, 23 Apr 2008 14:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.55.0804231544150.31934@cliff.in.clinika.pl> (raw)
In-Reply-To: <480F1BFF.5040305@st.com>
On Wed, 23 Apr 2008, Denis PILAT wrote:
> Thanks for this answer, but I don't understand why gdb.gdbtk does not
> belong to insight distribution.
Well, I suppose there is nothing to understand here -- I am not entirely
sure how exactly distributions from the src/ tree are prepared, but that's
quite likely a matter of the directory having been accidentally omitted
from the list in a script somewhere.
Maciej
next prev parent reply other threads:[~2008-04-23 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 6:51 testsuite/gdb.gdbtk Denis PILAT
2008-04-22 18:53 ` testsuite/gdb.gdbtk Maciej W. Rozycki
2008-04-23 11:23 ` testsuite/gdb.gdbtk Denis PILAT
2008-04-23 14:54 ` Maciej W. Rozycki [this message]
2008-04-23 18:12 ` testsuite/gdb.gdbtk Keith Seitz
2008-09-12 14:20 ` testsuite/gdb.gdbtk Denis PILAT
[not found] ` <48D30B30.4020407@redhat.com>
2008-09-20 20:41 ` testsuite/gdb.gdbtk Denis PILAT
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=Pine.LNX.4.55.0804231544150.31934@cliff.in.clinika.pl \
--to=macro@linux-mips.org \
--cc=denis.pilat@st.com \
--cc=insight@sources.redhat.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).