git-send-bugzilla (attached), is possibly the best thing since sliced bread. Maybe even better than sliced bread. It's how I submit all my patches to bugzilla.
There is an actually git branch somewhere on the interwebs (one of the gtk-webkit guys maintains it). But I don't remember the URL off hand. You'll need to make sure you've installed the SSLeay perl module (use CPAN) now that we've moved our bugzilla to https. It will even remember your username and password for you (although I forget how to set that up). -eric On Mon, Jun 23, 2008 at 8:34 AM, Michelangelo De Simone <[EMAIL PROTECTED]> wrote: > > Il giorno 23/giu/08, alle ore 14:01, Rob Kroeger ha scritto: > >> I have cloned the WebKit source tree with git and prepared a patch with >> git format-patch. >> Is this acceptable for attaching to the bug report or is there a better >> approach? > > Personally I make my patches with the old fashioned diff. Seen that you're > using git you may try to extract a patch with "git diff" (don't forget the > Changelog), comparing the actual (working) branch against the (untouched) > master could be a good idea to keep your work easily manageable. > > Obviously those two branches should be synced at the same commit, otherwise > you'll have a spurious patch with some else's code. > > git format-patch is mostly used for email submission. > > Hope this can help. > -- > // Et quid amabo nisi quod rerum enigma est? > > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > >
git-send-bugzilla
Description: Binary data
git-send-pastebin
Description: Binary data
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
