Re: [PATCH] shell32: Avoid some exception when property Set and Commit in shell32.dll

[Guillaume Gill]

Hi,

I sent this patch for the second time, and I not understand why it's not applicable...
It my first contribution, so maybe something forgotten in the process ?

Thanks for your support
________________________________
From: Marvin <testbot(a)winehq.org>
Sent: Thursday, April 19, 2018 11:54:31 PM
To: Guillaume Gill
Subject: Re: [PATCH] shell32: Avoid some exception when property Set and Commit in shell32.dll

Thank you for your contribution to Wine!

This is an automated notification to let you know that your patch has
been reviewed and its status set to "Apply failure".

This means that git-apply refused to apply the patch. This could be
either because it got mangled in transit, it's not relative to the
latest git, or it conflicts with someone else's patch in the same
area. You need to resend an updated patch.

If you do not understand the reason for this status, disagree with our
assessment, or are simply not sure how to proceed next, please ask for
clarification by replying to this email.

[PATCH] shell32: Avoid some exception when property Set and Commit in shell32.dll

[Austin English]

On Fri, Apr 20, 2018, 01:22 Guillaume Gill <gillg02(a)hotmail.fr> wrote:
> Hi,
>
> I sent this patch for the second time, and I not understand why it's not
> applicable...
> It my first contribution, so maybe something forgotten in the process ?
>
> Thanks for your support
> ------------------------------
> *From:* Marvin <testbot(a)winehq.org>
> *Sent:* Thursday, April 19, 2018 11:54:31 PM
> *To:* Guillaume Gill
> *Subject:* Re: [PATCH] shell32: Avoid some exception when property Set
> and Commit in shell32.dll
>
> Thank you for your contribution to Wine!
>
> This is an automated notification to let you know that your patch has
> been reviewed and its status set to "Apply failure".
>
> This means that git-apply refused to apply the patch. This could be
> either because it got mangled in transit, it's not relative to the
> latest git, or it conflicts with someone else's patch in the same
> area. You need to resend an updated patch.
>
> If you do not understand the reason for this status, disagree with our
> assessment, or are simply not sure how to proceed next, please ask for
> clarification by replying to this email.

Hi Guillaume,

Your patch doesn't apply to current master. Please rebase your patch and
resend.
>