> From: EXTERNAL van Riel Rob (ENTER, BT-CO/ENG1.1)
> Sent: dinsdag 6 maart 2018 09:51
> Subject: RE: [yocto] bitbake: git and patch problem
>
> The trail led me to discover I'd omitted a piece of information that I didn't
> know
> was relevant: the code I'm
> From: EXTERNAL van Riel Rob (ENTER, BT-CO/ENG1.1)
> Sent: maandag 5 maart 2018 16:12
> Subject: RE: [yocto] bitbake: git and patch problem
>
> > From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> > Sent: maandag 5 maart 2018 15:09
> > Subject: Re:
> -Original Message-
> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> Sent: maandag 5 maart 2018 15:09
> Subject: Re: [yocto] bitbake: git and patch problem
>
> Out of curiosity .. why is that unexpected, or inconvenient ? I never want a
> git
> repository to have dirty/unch
> From: Robert P. J. Day [mailto:rpj...@crashcourse.ca]
> Sent: maandag 5 maart 2018 12:13
> Subject: Re: [yocto] bitbake: git and patch problem
>
> On Mon, 5 Mar 2018, EXTERNAL van Riel Rob (ENTER, BT-CO/ENG1.1) wrote:
>
> > I'm experiencing strange (at least to my
I'm experiencing strange (at least to my eyes) behaviour from bitbake. My
recipe specifies a git repository as the main SRC_URI, then, in a variant
created using an append file adds a patch like this:
SRC_URI_append_mystuff += "file://mystuff.patch"
As expected, this grabs the sources from the
