2009/8/19 Barry Warsaw <[email protected]>: > I think we have to, because if I had to read all that to look at some > unfamiliar code in an unfamiliar VCS, I think I'd run away quickly! > > I'm not sure all that information is necessary though. Thinking about how I > make commando patches, I really want to just grab the code and start hacking > immediately. So the 'get a copy' instructions are crucial and I don't care > right away if that's got built-in efficiencies for later, and I probably > don't even care about pushing changes back. Maybe I'll make a patch or > maybe I'll abandon my hacking when I realize what a hornets nest the code > is. Point being, when there's a bug in some foreign code that's annoying me > and that I think I can fix, I really want to go from threshold-of-pain to > debugging-a-local-running-copy in as few steps as possible. I don't need to > know anything about git to run some monkeycommand to get a local copy of the > source.
I'm not suggesting we should have all that inline in the page, of course, just that we need at least a link to the guide. -- Martin <http://launchpad.net/~mbp/> _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
