[PATCH] aiaiai: allow defining checkpatch.pl location

Keller, Jacob E jacob.e.keller at intel.com
Tue Feb 4 12:05:09 EST 2014

On Tue, 2014-02-04 at 18:25 +0200, Artem Bityutskiy wrote:
> On Tue, 2014-02-04 at 18:21 +0200, Artem Bityutskiy wrote:
> > > Why clone the tree? There's a much saner way to do this.
> > 
> > But this is what we do anyway as the very first step in
> > 'aiaiai-test-patchset': we clone with --shared.
> Just to remind - the reason why we clone is because we cannot rely on
> the state of the original git tree. It does not have to have any
> specific refspec currently checked out. It may be even a bare tree.
> And one of the implementation goals was also to never touch the original
> git tree, treat it as read-only. So clone it, make our own copy, and
> then do everything with a local copy.
> Does this make sense?

Yes, I understand why we clone the development tree. I was referring to
what if the "coccinelle" and "checkpatch.pl" tree is located separately.

I completely understand why you treat the project tree as read-only. You
can actually do:

git show ref:scripts/checkpatch.pl where ref is any commit that your
second clone has access too, so that you don't need to do a separate
checkout. Archive would be better for this simply because it supports
directories though.

If we're using the same tree, I have no issue, I just thought it would
point to a separate tree.


More information about the aiaiai mailing list