Excerpts from Jimmy Huang's message of Wed Aug 18 07:12:41 +1000 2010: > > 0) I'd like to be credited for work I do - it's fairly common > > practice, and it generally helps encourage people to do more of it in > > the future. > > > > This refers to ivihome commits a2f219cee109f2247aacd669c7243be4331fec68, > > c5c9eceda864a400418d71849cb01f07f3dd34e3, and commit > > d5c8e99be0d301c820e90bed7ba77ea2a101c45a from ividesktop. > > > > I understand that at least the ivihome project commit was modified from > > my > > submission, however, a "based on work by ____" isn't out of place there. > > I am still new to accepting patches, so I'll make sure I keep this in > mind. A great thanks for the patch.
That's fine, and no problem. I hope to find the time to do some more work on IVI in the future. git send-email (which I use to send patches) and more generally git format-patch shove all details relating to the patch (commit message, author, date, etc) into the patch itself, so if you apply directly from that patch (instead of doing it by hand) then you get author info/etc for free and it tends to be a lot less work. If you use a mail client that supports piping mails (headers and all) then applying patches becomes very, very easy. I use 'sup' (http://sup.rubyforge.org/) - all I need to do to apply a patch is press | (the command for piping a mail to an external program) when reading a patch, and tell it to pipe to something like.. cd ~/code/rb-ivihome && git am Hope this helps, -- Robin Burchell http://rburchell.com _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
