On Sat, Jan 07, 2012 at 09:38:40AM -0800, Mike Melanson wrote: > On 1/7/2012 9:27 AM, Diego Biurrun wrote: > >Play around with the --dry-run and --annotate options of git-send-email. > > Cool, but I'm just not seeing how that offers any benefit over git > format-patch; git send-email. Maybe for people who are *really* sure > of what they're sending. I have to review my stuff about 5 times > before I send it.
Same workflow here - I review my stuff countless times before sending. It's something like [hack, hack, hack] git add -p git commit git add -p git commit ... [hack, hack, hack] git rebase -i [hack, hack, hack] git rebase -i ... [this looks ok finally] git log git log -p [hack, hack, hack] git rebase -i [this looks ok - this time for real] git log git log -p git cherry -v git send-email --dry-run HEAD~X git send-email --dry-run HEAD~Y <--- X != Y git send-email HEAD~Y but it's nice to skip opening your mail program and attaching patches and whatnot. With --in-reply-to you don't even break threads. Most importantly: you cannot forget to attach a patch! So in a nutshell: get used to Git a bit more, you'll love it soon enough and also come to like the moderately advanced features like send-email. Diego _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
