-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Daniel Campbell: > On 02/03/2016 04:57 PM, gokt...@binghamton.edu wrote: >> From: Gokturk Yuksek <gokt...@binghamton.edu> > >> Hi, > > [...] > > This isn't related to what you're doing but I felt it was a good > place to ask: > > How are you and other developers creating these series of e-mails? > It seems really handy and I'd like to know what it is, in the > event that I need to do the same. > >
Here's how I do it: Make your commits on a separate branch as if you'd push them directly to the repo. Use 'git format-patch' to generate patch files and use 'git send-email' to send them. You can skip format-patch and just use send-email but for a changeset of 21 commits I'd like to take another look. git format-patch --stat --summary -o bug558642_v3/ -n -v3 - --cover-letter master..devmanual-git-migration-v3 Creates the patches. '--cover-letter' creates a special patch file that requires editing which becomes the first email in the series, which is the one you replied to. Once satisfied, I sent it with: git send-email * Keep in mind that git will CC authors of the patches and yourself to the email. So you may have to adjust those. Don't forget to edit your .gitconfig and set proper SMTP options in the [sendemail] section. - -- gokturk -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJWsq3CAAoJEIT4AuXAiM4zuIEH/AvY3LYbcPMONlA5KuXTYTBG 8AtgqynEmQ0Qt1XujbC8W2bsKRMiUi8Xbtttnm/urfVCzCDKVQrzIkIA4x4kqIxA HKYgLuqE2zLxfLrbJkB0W3F1ogNOt1fuxzR9HSlasgqOSh13tpexINvI77iC4U0T 7ZlUeRv5R7AqvObEZO+2hY3JkHCELgD4lwRkNwjzqNVqJLJOVUev3wXid38GBPf2 qQUEUdZw5XuM5ygFM0r5ZgP2X8HEs5FfB9ouAHGuw7d/Kr+R3L+vH1v5g4+D+n1f iink8nR2LMrcBRiQ4/tbXyBgBiu/jZeG5UTJfQte3jyOuP4kf65SFADW+3B4+cc= =46ba -----END PGP SIGNATURE-----
