Thank you very much Amin. > On May 19, 2019, at 11:08, Amin Bandali wrote: > > The CONTRIBUTE [0] file in the Emacs repository should contain the > information you need with regards to the logistics of using git like > branching and the like. > > [0]: https://git.savannah.gnu.org/cgit/emacs.git/tree/CONTRIBUTE There is a discovery issue here because when you go to Savannah (https://savannah.gnu.org/projects/emacs/) you don't find that kind of information and instead find a link to EmacsWiki. What is the best way to propose changes to the Savannah top page ? Also, the Savannah page links to https://www.gnu.org/software/emacs/ which is beautifully designed but has no information about "contributing" or "developing" even in "Further information". What is the best way to propose changes to the gnu/emacs page ? > In short, usually you would develop on a local branch created from > latest master. When you’re done and/or when you’d like to show your > work to others and get feedback, you create a patch from your changes, > e.g. using git-format-patch, and use your mail client to send it to the > correct mailing list for the project. In the case of Emacs, that would > be one of emacs-devel@gnu.org (this list) or bug-gnu-emacs@gnu.org, > depending on the nature of your patch and e.g. if you’re fixing an > existing bug. I skimmed through the first link in your email, and it > does mention format-patch at some point. That's what I found out eventually. But the EmacsWiki pages don't really address people who don't have write access so I was a bit confused. > On a side note, instead of creating a patch with git-format-patch and > then sending it separately, you could also use git-send-email to create > a patch and send it at once. There’s a nice interactive tutorial for > git-send-email over at https://git-send-email.io that walks you through > setting up and using git-send-email to create and send patches to a > project mailing list. Thank you. > Hope this helps. Very much. Thank you again. Jean-Christophe Helary ----------------------------------------------- http://mac4translators.blogspot.com @brandelune