From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: sami wagiaalla <swagiaal@redhat.com>
Cc: Keith Seitz <keiths@redhat.com>, archer@sourceware.org
Subject: Re: [expr-cumulative] testsuite: Status of the tests upstreaming
Date: Mon, 24 Jan 2011 18:12:00 -0000 [thread overview]
Message-ID: <20110124181230.GA22988@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <4D3DAFEA.2080701@redhat.com>
Hi Sami,
On Mon, 24 Jan 2011 17:59:22 +0100, sami wagiaalla wrote:
> > namespace-nested-imports.exp (*) -> (not sure) namespace-nested-import.exp
>
> This correct. The test has not been renamed to make it 8.3 compatible.
The renaming applies to the other testcases. But this specific
namespace-nested-import{,s}.exp testfile has very different content - so I was
not sure if it really tests what the former test did test.
If the rename rule applies even in this case then sure everything is OK.
Thanks,
Jan
next prev parent reply other threads:[~2011-01-24 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 15:22 Jan Kratochvil
2011-01-14 15:36 ` Jan Kratochvil
2011-01-24 16:59 ` sami wagiaalla
2011-01-24 18:12 ` Jan Kratochvil [this message]
2011-01-24 20:44 ` sami wagiaalla
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=20110124181230.GA22988@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=archer@sourceware.org \
--cc=keiths@redhat.com \
--cc=swagiaal@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).