git patch work-flow(was: Re: Updated: Enabling tap interfaces in pfinet)
Michael Banck <[email protected]> Thu, 30 Jul 2026 14:27:32 +0200
| Newsgroups | gmane.os.hurd.bugs |
|---|---|
| Message-ID | <[email protected]> |
Hi, On Thu, Jul 30, 2026 at 03:22:08AM +0100, Bradley Morgan wrote: > ack, and + you could paste the patch file, the contents, directly into= =20 > your client and send it, for series just reply to the email you sent. That sounds like a recipe for apply-conflicts due ot copy-paste mangling tabs & spaces etc. =20 > It's very silly how copying in attachments is like, people dont do that = in > Linux for a reason=20 Conversely, the PostgreSQL development mailing list only deals with patches as attachments, not inline, and everybody there manages to cope. Just because one open source community has one particular work-flow does not mean every other one should have the same. In my opinion the correct work-flow on bug-hurd is "whatever bests works with Samuel" and then "if more than one things works ok with him, use whatever most others do as well". Michael