On 28/08/2018 09:57, Stephen J. Turnbull wrote:
> Michael Felt (aixtools) writes:
>
> > When building out of tree there is no .git reference. If I
> > understand the process it uses git to see what files have changed,
> > and does further processing on those.
>
> Just guessing based on generic g
Michael Felt (aixtools) writes:
> When building out of tree there is no .git reference. If I
> understand the process it uses git to see what files have changed,
> and does further processing on those.
Just guessing based on generic git knowledge here:
If you build in a sibling directory of t
When building out of tree there is no .git reference. If I understand the
process it uses git to see what files have changed, and does further processing
on those.
As to workflow, that may be better, but other than the name, unknown to me.
Sent from my iPhone
> On 24 Aug 2018, at 19:37, Mari
On Fri, Aug 24, 2018 at 1:22 PM Michael wrote:
>
> I am trying to be a 'good scout' and run "make patchcheck" more
> regularly. However, I generally am not successful because I build and
> test in separate directories.
There is an open issue about supporting out-of-tree builds:
https://bugs.pytho
I don't quite understand the problem you're facing with git and make
patchcheck?
Also, perhaps this is more for core-workflow instead of python-dev.
Mariatta
ᐧ
On Fri, Aug 24, 2018 at 3:20 AM Michael wrote:
> I am trying to be a 'good scout' and run "make patchcheck" more
> regularly. However
I am trying to be a 'good scout' and run "make patchcheck" more
regularly. However, I generally am not successful because I build and
test in separate directories.
There is access to git! just no ready reference in the build area.
So, not calling it a bug - but if someone else also experiences th
