Well, Dscho's intentions was, as the project name says, to simply send
patches unflowed. I have, however, had many other features which I
would like to see in a Git extension, which is why called it
ThunderGit instead. First I want the extension to help with Best
Practices for sending patches. Second, I want the extension to have
neatness like:
1) Saving a whole patch series as a mailbox, for easy apply. Maybe
even a "create new branch based on <branch>, and apply series"
feature? ^shrug^
2) Send patch (series) based on a selected email
(ie. setting "references" based on selection)
3) Showing Git patches with diff coloring (maybe also in the
editor, but mostly for received mails)
4) Basic validation of patch before sending, like
a) trailing whitespace
b) consistent preceding whitespaces
c) <add favorite>
This is my first extension though, so any help from people "in the
know" would be great!
If all attempts fail to make the extension fool proof wrt sending
proper unflowed patches, we could always just use Thunderbird as the
front-end for 'git send-email' ;-) I'm almost tempted to already go
that route, simply to avoid all the hassle. Then we could also just
use the plaintext composer, instead of the HTML composer which isn't
exactly "fool proof" for plaintext patches.
--
.marius
--
