CEPH filesystem development
 help / color / mirror / Atom feed
From: "Piotr Dałek" <branch@predictor.org.pl>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Little update on the build platform
Date: Tue, 31 May 2016 20:16:12 +0200	[thread overview]
Message-ID: <20160531181612.GE20357@predictor> (raw)
In-Reply-To: <1322819826.97774670.1464717769627.JavaMail.zimbra@redhat.com>

On Tue, May 31, 2016 at 02:02:49PM -0400, Erwan Velu wrote:
> That's pretty easy for a human to determine if a PR does affect the code.
> If we'd like to automate that, that would mean having a list of files known not to need triggering a rebuild and updating that list everytime a new file is added/retired.

How about ignoring everything that is under /doc/ and not under /doc/man/?
Seems like it would do the trick most of the time...

-- 
Piotr Dałek
branch@predictor.org.pl
http://blog.predictor.org.pl
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-05-31 18:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1236727659.97766119.1464716235552.JavaMail.zimbra@redhat.com>
2016-05-31 17:49 ` Little update on the build platform Erwan Velu
2016-05-31 17:58   ` Piotr Dałek
2016-05-31 18:02     ` Erwan Velu
2016-05-31 18:16       ` Piotr Dałek [this message]
2016-05-31 18:44   ` John Spray
2016-05-31 19:14     ` Ken Dreyer
2016-06-01 14:40       ` Erwan Velu
2016-06-01 14:57         ` Sage Weil
2016-06-02  8:11   ` Nathan Cutler
2016-06-13 15:41     ` Ken Dreyer

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=20160531181612.GE20357@predictor \
    --to=branch@predictor.org.pl \
    --cc=ceph-devel@vger.kernel.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