public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Matt Fleming <matt@console-pimps.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Dont-Auto-Build
Date: Sat, 21 Sep 2013 16:27:10 +0800	[thread overview]
Message-ID: <20130921082710.GA30273@localhost> (raw)
In-Reply-To: <20130920143659.GA10591@pd.tnic>

Hi Borislav,

On Fri, Sep 20, 2013 at 04:36:59PM +0200, Borislav Petkov wrote:
> Hey Fengguang,
> 
> do you still grep for "Dont-Auto-Build" in all the commit messages of a
> branch which is not supposed to be tested?

Yes.

> Or can I tag the branch name to make it more explicit for everyone?

If you name the branch *-experimental, it will be skipped by the robot.

Thanks,
Fengguang

  reply	other threads:[~2013-09-21  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 14:36 Dont-Auto-Build Borislav Petkov
2013-09-21  8:27 ` Fengguang Wu [this message]
2013-09-21 10:10   ` Dont-Auto-Build Borislav Petkov

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=20130921082710.GA30273@localhost \
    --to=fengguang.wu@intel.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@console-pimps.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