Hi, On Fri, Mar 25, 2022 at 06:10:10PM +0100, Michael Baentsch wrote: > I'm not quite sure I understand what you're asking me to do. Why not > simply use standard github cooperation mechanisms?
Because our master repo is not "on github", and we do patch review
via the mailing list, with archived public ACKs, and list archive
URLs included in the commit message. So it is very clear how a
certain code change came into our tree.
(Is this highly annoying and very much time consuming? Yes...
but also "is this appropriate for software handling people's most
sensitive data packets?" - and the answer for that is "yes!" as
well... :-) )
> $ git send-email --to=openvpn-devel@lists.sourceforge.net HEAD~1
> git: 'send-email' ist kein Git-Befehl. Siehe 'git --help'.
>
> Pardon the German of my computer: It says "send-email" is no known git
> command.
Seems your distribution split this part of git into a separate package
(propably to avoid the dependency on a mail transport agent).
Of course you can do "git format-patch" and then send the result with
a regular mail client - but we've found out (the hard way) that most
mail clients mistreat patches one way or the other - breaking long
lines, reformatting whitespace, ... - so the end result does not
apply anymore. "git send-email" works around this.
If you do not succeed in this, one of us can take the patch from the
PR and send it to the list.
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
