Re: Updated: Enabling tap interfaces in pfinet

Bradley Morgan <[email protected]> Thu, 30 Jul 2026 03:22:08 +0100
Newsgroups gmane.os.hurd.bugs
Message-ID <[email protected]>
On July 30, 2026 2:49:48 AM GMT+01:00, Damien Zammit <[email protected]>
wrote:
>You can use git send-email --no-format-patch and pass it a patch file
>directly then it can be sent from any host with SMTP available.
>
>Hope that helps,
>Damien
>

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.


It's very silly how copying in attachments is like, people dont do that in
Linux for a reason 


>
>Sent from Proton Mail for Android.
>
>-------- Original Message --------
>On Thursday, 07/30/26 at 10:06 Ralph Ronnquist <[email protected]> wrote:
>On Thu, Jul 30, 2026 at 12:39:15AM +0100, Bradley Morgan wrote:
>> On 30 July 2026 00:30:07 BST, Samuel Thibault <[email protected]>
>> wrote:
>> >Bradley Morgan, le jeu. 30 juil. 2026 00:28:13 +0100, a ecrit:
>> >> On 30 July 2026 00:16:41 BST, Ralph Ronnquist <[email protected]>
>wrote:
>> >> >Fair enough. I've attached the merged patch here, and then took the
>> >> >opportunity to fix up the tap mac address logic as well.
>> >> >
>> >> >There's still a problem in using a direct mapping of the tap name to
>> >> >mac address since then a virtual cable between two hosts will
>require
>> >> >there being differently named taps. Perhaps it really needs an
>> >> >additional pfnet argument for that.
>> >> >
>> >>
>> >> I'm still concerned as to why people in hurd sends their patches as
>> >> attachments...
>> >
>> >That's really not a problem to me when it's properly identified as a
>> >text attachment, when I reply with mutt it gets inlined automatically.
>>
>> My concern is that some clients aren't as lucky, could users send the
>> patches contents either through their client, or through a alternate
>tool
>> like git send-email? So people like me can review without paining myself
>> By opening the file and copy and pasting the context, which
>> gets pretty annoying
>
>Hmm I thought it sends as a normal mime-encoded email with
>attachment(s). That's what I get. Isn't that what you get, Bradley?
>
>For me, the (hurd) host that holds the git workspace doesn't have any
>MTA setup, and I use the procedure to prepare the patch with git
>format-patch, transfer that to an emailing capable host and then email
>it from there. (as attachment with mutt). I suppose g-t-email is
>available, but thn my hurd host will need to be on the Internet, and
>have a bit more administrative setup with keys (I'm not sure I would
>want those stored on an experimental system).


Just copy the contents into ur client


>Though I'm of course willing to adapt to the procedural habits
>expected or "required" by the group where I wish to conribute. My
>intention is to contribute in a useful way.

I mean, it's a good thing, and you seemingly are contributing usefully


>regards,
>
>Ralph.
>
>
>

Thanks!