| Message ID | 20191026005159.98405-1-emilyshaffer@google.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | some clarifications to MyFirstContribution | expand |
Emily Shaffer wrote: > [1/3] Per SZEDER's comment, we should be adding `git psuh` to the list > of commands used by 'git help'. > [2/3] Outreachy applicant Heba Waly indicated that the tutorial doesn't > cover dependencies needed to build Git. Oh! It's also a good idea to give these people credit for their contribution, via a Reported-by in the commit message. Sorry I missed it before (I tend to read the patches first and cover letter last, which is good for ensuring the commit messages are self contained enough to be helpful when the patch gets dug up in history later, but not so good for noticing this kind of thing). Thanks, Jonathan
Hi all, With the wave of Outreachy participants (hello! welcome!) a few shortcomings in the MyFirstContribution tutorial have been noted; plus, a comment from SZEDER (thanks!) sent along some weeks ago about a missing step in the new command process. [1/3] Per SZEDER's comment, we should be adding `git psuh` to the list of commands used by 'git help'. [2/3] Outreachy applicant Heba Waly indicated that the tutorial doesn't cover dependencies needed to build Git. However, I don't have a good handle on what's needed for platforms besides Linux, so I really appreciate others suggesting dependency installation steps for other platforms (even if it is a link to another guide). [3/3] Per some discussions in #git-devel this week, it's not apparent who to ask for the /allow comment to tell GitGitGadget that you can be trusted. So, add the same hint which is proposed to be shown in GitGitGadget's welcome message. Emily Shaffer (3): myfirstcontrib: add 'psuh' to command-list.txt myfirstcontrib: add dependency installation step myfirstcontrib: hint to find gitgitgadget allower Documentation/MyFirstContribution.txt | 57 +++++++++++++++++++++++++-- 1 file changed, 54 insertions(+), 3 deletions(-)