Baby steps for patch submission?
Greetings with wishes of health and peace. I've been programming for a long time, but have never contributed to a project. My programming has been building mouse driver and graphics acceleration libraries using X86 assembly for DOS programs, serial communications (simple terminal emulator) using Mix PowerC atop DOS, file-manipulation utilities using Sun cc, and Perl/CGI with DBI. I've now made to small edits necessary to correct the links on the about:splash, and need to know the best way to create and submit a patch. I made the edits in a copy of the source for 0.6.6 that I obtained through Debian. Is the best diff to diff -pru <mySrcDir> <origSrcDir>, or just to diff the edited file with the original file? Do I email the patch, or check it in to the CVS server? -- _______________________________________________ Get your free email from http://mymail.operamail.com Powered by Outblaze
Hello Volando! Voland0 De Caribilla writes:
Greetings with wishes of health and peace.
[...] To start of you can read this text from the site: http://dillo.auriga.wearlab.de/developer.html
I've now made to small edits necessary to correct the links on the about:splash, and need to know the best way to create and submit a patch. I made the edits in a copy of the source for 0.6.6 that I obtained through Debian. Is the best diff to diff -pru <mySrcDir> <origSrcDir>, or just to diff the edited file with the original file?
Actually the diff command must contain the original dir first, then your source. To diff the entire directory is the recommended if you have changed more than one/few files. Of course, if you have only changed one file, it's ok to do: diff -pru dillo.orig/this_file dillo.my.version/this_file Oh, and it is prefered if you diff against current CVS not old versions. Check here: http://cvs.auriga.wearlab.de/cgi-bin/cvsweb.cgi/dillo/ to see if the files in question were changed.
Do I email the patch, or check it in to the CVS server?
You can't really check it into the CVS. The CVS is only public for reading, only Jorge and Sebastian have access for writing. If the patch is "small" (I'm guessing like 10-20KB, but maybe Jorge has a different opinion) I guess it's ok to send it directly to the list. If it's bigger, than you should put it up somewhere in the Internet. best regards, -- Livio <livio@ime.usp.br>
participants (2)
-
Livio Baldini Soares -
Voland0 De Caribilla