public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: 汤孟 <tangmeng@uniontech.com>
To: "Cyril Hrubis" <chrubis@suse.cz>, "Li Wang" <liwang@redhat.com>
Cc: "LTP List" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] link/link02: Convert to new API
Date: Mon, 25 Oct 2021 16:25:24 +0800	[thread overview]
Message-ID: <tencent_019185364707BDF116DD7C74@qq.com> (raw)
In-Reply-To: <YXZmuCPM1kdBG/eo@yuki>


[-- Attachment #1.1: Type: text/plain, Size: 1250 bytes --]

Hi,&nbsp;Cyril Hrubis and LI Wang!


First of all, I want to say that I am extremely sorry.
Since it was the first time I submitted a patch here, there were many unfamiliar and misunderstandings in the process, which led to multiple submissions.
I will take care to avoid this problem in the future


--&nbsp;
Regards,
TangMeng
------------------&nbsp;Original&nbsp;------------------
From: &nbsp;"Cyril Hrubis"<chrubis@suse.cz&gt;;
Date: &nbsp;Mon, Oct 25, 2021 04:10 PM
To: &nbsp;"Li Wang"<liwang@redhat.com&gt;; 
Cc: &nbsp;"tangmeng"<tangmeng@uniontech.com&gt;; "LTP List"<ltp@lists.linux.it&gt;; 
Subject: &nbsp;Re: [LTP] [PATCH] link/link02: Convert to new API

&nbsp;

Hi!
&gt; Plz stop sending the same patch again and again. It looks
&gt; like an email bomb to the mailing list.

Partly my mistake, when I looked at the list of patches for moderation I
didn't realized that this is one patch send many times, sorry for that.

However Tang if you email to a ML is held for moderation please wait
instead of resending, I do reviewe the held emails nearly daily so the
delay shouldn't be worse than a day or two. Also if you sing up to the
ML the emails would go right through.

-- 
Cyril Hrubis
chrubis@suse.cz

[-- Attachment #1.2: Type: text/html, Size: 1970 bytes --]

[-- Attachment #2: Type: text/plain, Size: 60 bytes --]


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2021-10-25  8:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  4:38 [LTP] [PATCH] link/link02: Convert to new API tangmeng
2021-10-25  8:04 ` Li Wang
2021-10-25  8:11   ` Cyril Hrubis
2021-10-25  8:25     ` 汤孟 [this message]
2021-10-25  8:36       ` Li Wang
2021-10-25  8:30 ` Li Wang
  -- strict thread matches above, loose matches on Subject: below --
2021-10-25  2:27 tangmeng
2021-10-22  4:35 tangmeng
2021-10-22  4:34 tangmeng
2021-10-22  4:29 tangmeng
2021-10-22  4:24 tangmeng
2021-10-22  3:44 tangmeng
2021-10-22  3:43 tangmeng
2021-10-22  3:42 tangmeng
2021-10-22  3:40 tangmeng
2021-10-22  3:34 tangmeng
2021-10-22  3:30 Tang Meng
2021-10-25  8:29 ` Cyril Hrubis

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=tencent_019185364707BDF116DD7C74@qq.com \
    --to=tangmeng@uniontech.com \
    --cc=chrubis@suse.cz \
    --cc=liwang@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox