From: Damien Lespiau <damien.lespiau@intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] RELEASING: Fix releasing instructions to match the latest release.sh
Date: Fri, 20 Mar 2015 15:57:45 +0000 [thread overview]
Message-ID: <20150320155745.GA3687@strange.ger.corp.intel.com> (raw)
In-Reply-To: <550B09BA.2050908@gmail.com>
On Thu, Mar 19, 2015 at 05:39:06PM +0000, Emil Velikov wrote:
> On 19/03/15 16:35, Damien Lespiau wrote:
> > - Running "make distcheck" should result in no warnings or errors
> > - and end with a message of the form:
> > + Verify that the code passes "make distcheck". Running "make
> > + distcheck" should result in no warnings or errors and end with a
> > + message of the form:
> >
> Side note: Pretty sure that current make distcheck produces a handful of
> warnings ;-)
Yup, it does, that'll have to be for another time though.
> Although we'll try to have them sorted by next release.
That'd be excellent.
> With my comment in patch 2 and Ilia's in 3 the series is
> Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
Done and pushed, thanks for the review!
--
Damien
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-03-20 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 16:35 [PATCH 0/3] A few fixes in the libdrm release documentation Damien Lespiau
2015-03-19 16:35 ` [PATCH 1/3] RELEASING: Fix releasing instructions to match the latest release.sh Damien Lespiau
2015-03-19 17:39 ` Emil Velikov
2015-03-20 15:57 ` Damien Lespiau [this message]
2015-03-19 16:35 ` [PATCH 2/3] RELEASING: Fix the step numbering Damien Lespiau
2015-03-19 17:32 ` Emil Velikov
2015-03-19 17:36 ` Damien Lespiau
2015-03-19 16:35 ` [PATCH 3/3] RELEASING: Fix annouce typo Damien Lespiau
2015-03-19 16:39 ` Ilia Mirkin
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=20150320155745.GA3687@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.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 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.