On Tue, Aug 8, 2017 at 2:42 AM, Christopher Li <sparse@xxxxxxxxxxx> wrote: > On Mon, Aug 7, 2017 at 8:23 PM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> 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 Are you sure? in the link I pasted here above, the git branch is: git://github.com/lucvoo/sparse.git fix-nested-pseudo-users-deletion-v4 aka: bddf7d1e4ed81c3def7c6de2796a5489ca678399 > I actually prefer to use git pull if it is available to use. Good. > 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. It won't change anything, in both case it's just a name for something (and using specific name for specific thing is a good thing I think) but no problem, it's fine for me. I'll sent a proper pull request. > 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. Make sense. -- Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
