2017-03-13 2:09 GMT+03:00 chdiza <[email protected]>: > Now contrast that with Vim. Even though we know @dpelle has authored at > least 1 > commit, this will show none: > > That's not the way that one should go about looking for authorship for Vim > patches, and it never has been. Grep the git log if you want to know those > things. > > Vim is only on github in the first place because googlecode shut down and a > cadre of loud users browbeat Bram into putting it here rather than > Bitbucket. This repo does not follow the usual github conventions wrt > workflows and such, so you need to stop expecting it to.
There are typos and I know myself that I am referred to as, at least, `ZyX`, `Nikolay Pavlov` and `Nikolai Pavlov`. This makes searching via git (e.g. `git log --grep` or regular search in `less`) tricky. When one uses git or mercurial own capabilities to specify author and pulls in original commits, at least, there is only author to blame for typos, not Bram. It is also possible to pull in a PR, squash it, reword the commit message, do some fixups and git will still keep original author. Last, but not least: both git and mercurial always allowed to specify author on the command-line explicitly when doing `vcs commit`, even though this variant is still prone for typos. So making “the right thing” was possible back then on google code, just there were not much uses for it. PS: github vs bitbucket has nothing to do with this. Requests to change the workflow have very long history: current workfolw is exceptional for opensource projects and not in a good sense. And bitbucket just has less capabilities regarding the statistics, yet it is still able to link commits with the account. I am not entirely sure how GH and BB will swallow authors specified with `vcs commit --author` (`--user` for mercurial) though, but I guess they will be fine unless there are signatures involved. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > > -- > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
