[PATCH util-modular] release.sh: Also update srv_path for older Mesa releases.

Emil Velikov emil.l.velikov at gmail.com
Mon Feb 27 11:56:32 UTC 2017


On 27 February 2017 at 01:50, Peter Hutterer <peter.hutterer at who-t.net> wrote:
> On Fri, Feb 24, 2017 at 04:09:06PM +0000, Emil Velikov wrote:
>> On 14 February 2017 at 11:39, Emil Velikov <emil.l.velikov at gmail.com> wrote:
>> > From: Emil Velikov <emil.velikov at collabora.com>
>> >
>> > Otherwise we'll be missing the "$version" directory and the files
>> > will be uploaded the the wrong location.
>> >
>> > Fixes: f16477858bc "release.sh: remove $MESA_VERSION from the
>> > destination location"
>> > Signed-off-by: Emil Velikov <emil.velikov at collabora.com>
>> > ---
>> >  release.sh | 1 +
>> >  1 file changed, 1 insertion(+)
>> >
>> > diff --git a/release.sh b/release.sh
>> > index c894063..c824dea 100755
>> > --- a/release.sh
>> > +++ b/release.sh
>> > @@ -580,6 +580,7 @@ process_module() {
>> >          # Prior to 17.0.x Mesa uses separate folder for each release
>> >          if test `echo $mesa_version | cut -d'.' -f1` -lt 17; then
>> >              section_path=$section_path/$mesa_version
>> > +            srv_path="/srv/$host_current/www/$section_path"
>> >              echo "Info: creating mesa directory on web server:"
>> >              ssh $USER_NAME$hostname mkdir -p $srv_path  &>/dev/null
>> >              if [ $? -ne 0 ]; then
>> > --
>> > 2.11.0
>> >
>> Peter, others - humble ping ?
>
> I've pushed this one now:
>
> remote: Updating patchwork state for https://patchwork.freedesktop.org/project/Xorg/list/
> remote: I: patch #138807 updated using rev f570660a8fd3a307ce9ccd112563e52e9696d334.
> remote: I: 1 patch(es) updated to state Accepted.
> To git+ssh://git.freedesktop.org/git/xorg/util/modular
>    b23d0b9..f570660  master -> master
>
>> There's a bunch of other patches of mine [for not so loved parts of
>> xorg], which seems to be in limbo [1].
>> Should I poke them individually or can I apply for commit access to
>> xorg/ and push the trivial ones ?
>
> yes, applying for commit access is a good idea anyway :)
>
Do we have any tips/wiki how to do that ? I can only find this [1]
page which doesn't say much.

Guessing that I'll just open a bug-report against xorg/other ?

Thanks
Emil

[1] https://www.x.org/wiki/RepoPolicy/


More information about the xorg-devel mailing list