From: chrubis@suse.cz
To: Mike Frysinger <vapier@gentoo.org>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v2] ptrace: Fix build problems with glibc-2.18
Date: Thu, 9 Jan 2014 12:58:34 +0100 [thread overview]
Message-ID: <20140109115834.GE5125@rei.Home> (raw)
In-Reply-To: <201401081442.11349.vapier@gentoo.org>
Hi!
> > Let's keep it for the next release (which will happen anytime soon). The
> > ptrace tests are messy and the ptrace.h needs to be fixed anyway.
> >
> > Or do you insist on removing it before the release? I don't like that
> > idea much but I can change my opinion if you provide reasonable
> > arguments.
>
> we can leave it for a while, but i'll delete it once glibc-2.19 is out for
> some time
OK with me.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-01-09 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 10:12 [LTP] [PATCH v2] ptrace: Fix build problems with glibc-2.18 Markos Chandras
2013-12-02 9:31 ` Markos Chandras
2013-12-02 17:35 ` chrubis
2013-12-02 17:52 ` chrubis
2014-01-05 22:27 ` Mike Frysinger
2014-01-06 11:45 ` Markos Chandras
2014-01-06 12:49 ` Mike Frysinger
2014-01-08 11:50 ` Markos Chandras
2014-01-08 19:41 ` Mike Frysinger
2014-01-08 15:22 ` chrubis
[not found] ` <201401081442.11349.vapier@gentoo.org>
2014-01-09 11:58 ` chrubis [this message]
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=20140109115834.GE5125@rei.Home \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=vapier@gentoo.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