All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] ??????: [PATCH v2] cleanup: Unify the annotation style and remove Redundant code
Date: Wed, 17 Mar 2021 14:02:15 +0100	[thread overview]
Message-ID: <YFH910rpcVjzDuEI@pevik> (raw)
In-Reply-To: <32fcff9e-54d4-a4ed-0d4c-3b703921d035@163.com>

> On 3/17/21 8:13 PM, Petr Vorel wrote:
> > Hi,

> > > Hi!
> > > > I'd keep both: this is for cleanup of old approach, conversion in testinfo.pl in
> > > > case there is inconsistency in the future.
> > > If we agree on a certain format I would vote for docparse to fail the
> > > build if the format is wrong, that will force us to maintain the
> > > metadata correctly.
> +1
> > Make sense. But being the one who often fixes docparse failures I'm not sure if
> > I want to implement extra work for myself :).

> > (It'd help to implement https://github.com/linux-test-project/ltp/issues/599,
> > but I don't have any server to run it).

> This issue is about docparse, I think we can merge the patch itself
> directly.
Agree, rebased and merged with updated commit message.

Not sure when I update testinfo.pl to Cyril's suggestion,
anyone feel free to implement it.

Kind regards,
Petr

> Best Regards,

> Xiao Yang

  reply	other threads:[~2021-03-17 13:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 10:01 [LTP] [PATCH v2] cleanup: Unify the annotation style and remove Redundant code Zhao Gongyi
2021-03-17 10:57 ` Petr Vorel
2021-03-17 11:12   ` [LTP] 回复: " yangx.jy
2021-03-17 11:34     ` Petr Vorel
2021-03-17 12:09       ` [LTP] ??????: " Cyril Hrubis
2021-03-17 12:13         ` Petr Vorel
2021-03-17 12:32           ` Xiao Yang
2021-03-17 13:02             ` Petr Vorel [this message]
2021-03-17 12:09       ` [LTP] 回复: " Xiao Yang

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=YFH910rpcVjzDuEI@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.