Re: git patch work-flow(was: Re: Updat ed: Enabling tap interfaces in pfinet)

On 4 August 2026 22:04:05 BST, Bradley Morgan via Bug reports for the GNU
Hurd <[email protected]> wrote:
>On 4 August 2026 20:14:40 BST, Joshua Branson via Bug reports for the GNU
>Hurd <[email protected]> wrote:
>>
>>On 7/30/26 8:27 AM, Michael Banck wrote:
>>> 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
>>>> 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.
>>>   
>>>> It's very silly how copying in attachments is like, people dont do
>that
>>in
>>>> Linux for a reason
>>> 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
>>
>>
>>Also anyone feel free to take a look and update this web page that I
>made:
>>
>>
>>https://hurd.ion.nu/contributing/developer-workflows.html
>>
>>
>>
>
>
>Could we do a hurd documentation file 

Folder* oopsie

where it would be in .rst format?
>
>Instead of redirecting people to outside sites, I have the time to add
>initial documentation in the folder because I have time cuz it's like
>summer break
>
>Thanks!
>
>

Thanks!