Message ID | aa4aa155-b9b2-9099-b7a2-349d8d9d8fbd@paragon-software.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [GIT,PULL] ntfs3: new NTFS driver for 5.15 | expand |
On Fri, Sep 3, 2021 at 8:19 AM Konstantin Komarov <almaz.alexandrovich@paragon-software.com> wrote: > > https://github.com/Paragon-Software-Group/linux-ntfs3.git master Oh, I didn't notice this until now, as I was lining up to actually pull this. I probably forgot to say this originally: For github accounts (or really, anything but kernel.org where I can just trust the account management), I really want the pull request to be a signed tag, not just a plain branch. In a perfect world, it would be a PGP signature that I can trace directly to you through the chain of trust, but I've never actually required that. So while I prefer to see a full chain of trust, I realize that isn't always easy to set up, and so at least I want to see an "identity" that stays constant so that I can see that pulls come from the same consistent source that controls that key. (We've also had situations where the chain of trust just didn't exist _yet_, but then later on it can be established as a developer ends up becoming more integral in the community) Signed tags are easy to use - the hardest part is having any pgp key setup at all, then git makes using the keys trivial with "git tag -s .." Linus
On Sat, Sep 4, 2021 at 10:34 AM Linus Torvalds <torvalds@linux-foundation.org> wrote: > > For github accounts (or really, anything but kernel.org where I can > just trust the account management), I really want the pull request to > be a signed tag, not just a plain branch. Ok, to expedite this all and not cause any further pointless churn and jumping through hoops, I'll let it slide this time, but I'll ask that you sort out your pgp key for the future and use signed tags. Also, I notice that you have a github merge commit in there. That's another of those things that I *really* don't want to see - github creates absolutely useless garbage merges, and you should never ever use the github interfaces to merge anything. This is the complete commit message of that merge: Merge branch 'torvalds:master' into master Yeah, that's not an acceptable message. Not to mention that it has a bogus "github.com" committer etc. github is a perfectly fine hosting site, and it does a number of other things well too, but merges is not one of those things. Linux kernel merges need to be done *properly*. That means proper commit messages with information about what is being merged and *why* you merge something. But it also means proper authorship and committer information etc. All of which github entirely screws up. We had this same issue with the ksmbd pull request, and my response is the same: the initial pull often has a few oddities and I'll accept them now, but for continued development you need to do things properly. That means doing merges from the command line, not using the entirely broken github web interface. (Sadly, it looks like that ksmbd discussion was not on any mailing lists, so I can't link to it). Linus
The pull request you sent on Fri, 3 Sep 2021 18:19:50 +0300:
> https://github.com/Paragon-Software-Group/linux-ntfs3.git master
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f7464060f7ab9a2424428008f0ee9f1e267e410f
Thank you!