Re: Upcoming sparse release RC5

[Christopher Li <sparse@chrisli.org>]

On Mon, Aug 7, 2017 at 8:23 PM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> If you don't mind, it would be nice if you could use the pull request
> I sent here: http://marc.info/?l=linux-sparse&m=150188507213269&w=4
> (you never saw it because I copy-pasted "[PATCH v3]" in the title of
> the cover page instead of using "[PATCH v4]" and so used the v3 and
> corrected the s/list/__list/ by hand).
> But it's not very important.

I did not find that git pull url due to the V3 title. I did look for it.

When I look at the patch, there is some compile error on one of the
patch (patch 4?). I just fix it by hand. I assume the git pull has the
same error because the patch are generated from git.

I just checked, that compile error still on the git url you send out
in the email. I still can't use it

I actually prefer to use git pull if it is available to use.

Also, can you please give the pull request a dedicate branch,
like "for-chris",  not a tag? I don't want to pull from random branch
and end up merging between your topic branches.

I often need to seek clarify if this patches series is mean for merge.
If you make that in the dedicate pull branch, I will know for sure.
I can see that branch get updated from git fetch before I saw the
email.

Chris