From: Brian Paul <brianp@vmware.com>
To: Thierry Vignaud <thierry.vignaud@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] fix mesa tarball creation again
Date: Fri, 29 Apr 2011 17:56:52 -0600 [thread overview]
Message-ID: <4DBB5044.4040608@vmware.com> (raw)
In-Reply-To: <BANLkTikfVdr6d1T5dT_FC_qqXCE27H8gjg@mail.gmail.com>
On 04/28/2011 12:38 AM, Thierry Vignaud wrote:
> On 19 April 2011 16:35, Brian<brianp@vmware.com> wrote:
>>>> Pushed, thanks.
>>>
>>> Can you know commit this one that fixes missing files in the generated
>>> tarball
>>> so that one can build mesa out of the tarball?
>>> Thx
>>
>> I'll commit it soon. Thanks.
>
> Hi
> The following patch fix tarball creation again (removed files and one
> missing Makefile)
Thanks. I'll commit it soon.
-Brian
prev parent reply other threads:[~2011-04-29 23:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 8:11 [PATCH] fix mesa tarball creation again Thierry Vignaud
2011-04-17 23:27 ` Marek Olšák
2011-04-19 9:04 ` Thierry Vignaud
2011-04-19 14:35 ` Brian
2011-04-28 6:38 ` Thierry Vignaud
2011-04-29 23:56 ` Brian Paul [this message]
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=4DBB5044.4040608@vmware.com \
--to=brianp@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=thierry.vignaud@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox