On Sun, May 13, 2012 at 11:11 PM, jaseem abid <jaseemabid@xxxxxxxxx> wrote: > > Dear all, > > CC : Andrew Sayers, Jakub Narębski > > I have been working on gitweb for a couple of days as part of a > rejected GSoC proposal. I would love to get some help on this and if > somebody can, that would be thankful. > > 1. How is code tested after some change? I am not talking about unit > testing but about making sure that application is doing what it is > actually intended to do. Do you have to re - install git/gitweb with > every version of code you commit and make sure that it works well and > as expected? Or, is there some other way? Sorry but I am a newbie when > it comes to FOSS contribution and as well working on a project of this > magnitude. > > As far as I understand, gitweb by default is looking for files from > `/usr/share/gitweb/` (I work on Debian Sid if that helps). If I edit > the perl or some JavaScript code, how should I test it? *Install* my > version from source as mentioned in "gitweb/INSTALL" ? Adding a bit more to the last mail. In the specific case of gitweb, I can sym link files from `/usr/share/giweb` or any installation folder to the working directory for testing. Then all I have to do is to rebuild the files and forget about moving the files to right place. Is it ok to develop this way? I am looking for some good practices here on this. -- Jaseem Abid http://jaseemabid.github.com -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html