public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH 1/2] security/p9auth: Cleanup
Date: Tue, 9 Sep 2014 12:18:13 +0200	[thread overview]
Message-ID: <20140909101813.GA32553@rei> (raw)
In-Reply-To: <1409895039.17311.20.camel@G08JYZSD130126>

Hi!
> > So there is no reason to maintain the code or add it to default run
> > unless it's actually used somewhere.
> > 
> 
> OK, please ignore these patches.
> And, thank you.

Do we agree on removing the test entirely? Can you send such patch?

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2014-09-09 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12  6:05 [LTP] [PATCH 1/2] security/p9auth: Cleanup Zeng Linggang
2014-07-12  6:06 ` [LTP] [PATCH 2/2] security/p9auth: Add p9auth tests to default Zeng Linggang
2014-09-04 12:24 ` [LTP] [PATCH 1/2] security/p9auth: Cleanup chrubis
     [not found]   ` <1409895039.17311.20.camel@G08JYZSD130126>
2014-09-09 10:18     ` chrubis [this message]
     [not found]       ` <1410503722.8011.2.camel@G08JYZSD130126>
2014-09-17 11:51         ` [LTP] [PATCH] p9auth: remove this test Jan Stancek
2014-09-18  1:10           ` Zeng Linggang

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=20140909101813.GA32553@rei \
    --to=chrubis@suse.cz \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=zenglg.jy@cn.fujitsu.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