On Tue, Jan 14, 2025 at 12:32:05PM -0500, Brian Haley wrote:
> Should I re-propose it now as I think it was important.
>
Thanks for
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2025q1/017970.html
If email address ~stappers/dnsmasqm...@lists.sr.ht was added,
would the patch have bee
On Sat, Aug 17, 2024 at 06:38:52PM +, Dan Schaper wrote:
> From Geert Stappers, Date 8/17/2024 11:05:25 AM
> > On Sat, Jul 27, 2024 at 11:25:04AM +0200, Dominik Derigs wrote:
> > > Hey Simon,
> > >
> > > another patch ...
> >
> > IMNSHO should we, this mailinglist, help Simon where we can.
ate?
Dan
-- Original Message --
From "Geert Stappers"
To dnsmasq-discuss@lists.thekelleys.org.uk
Date 8/17/2024 11:05:25 AM
Subject [Dnsmasq-discuss] patches
On Sat, Jul 27, 2024 at 11:25:04AM +0200, Dominik Derigs via Dnsmasq-discuss
wrote:
Hey Simon,
another patch ..
On Sat, Jul 27, 2024 at 11:25:04AM +0200, Dominik Derigs via Dnsmasq-discuss
wrote:
> Hey Simon,
>
> another patch ...
IMNSHO should we, this mailinglist, help Simon where we can. Insteadof
just pushing work towards Simon.
Groeten
Geert Stappers
P.S.
I understand that Dominik **might** feel
In-Reply-To: <20200207220832.dsvb5gtd5g2by4ob@pali>
On Fri, Feb 07, 2020 at 11:08:32PM +0100, Pali Rohár wrote:
> Hello Simon!
>
> Could you please review / comment this patch?
>
> I would like to know what is needed to be fixed or changed,
> so patch could be finally merged.
Other DHCPv6 pa
On Mon, Feb 12, 2018 at 03:18:25PM -, Andy Hawkins wrote:
> In article , john doe wrote:
> > Idealy, you would clone the dnsmasq repository, then you would do your
> > changes then commit (git commit -s) them and finaly send the patch.
>
> I've already done most of that. I posted the output o
Thanks Simon!
On 10/06/15 22:49, Simon Kelley wrote:
On 10/06/15 10:57, Neil Jerram wrote:
Alternatively, here is the whole patch set again, regenerated so as to
incorporate those deltas at the appropriate places.
Many thanks for your time looking at these enhancements.
Regards,
Neil
On 10/06/15 10:57, Neil Jerram wrote:
> Alternatively, here is the whole patch set again, regenerated so as to
> incorporate those deltas at the appropriate places.
>
> Many thanks for your time looking at these enhancements.
>
> Regards,
> Neil
>
>
Many thanks. Patches applied, and 2.73rc
On 10/06/15 10:15, Neil Jerram wrote:
On 09/06/15 22:11, Simon Kelley wrote:
A couple of (very small quibbles)
-/* The source interface can only appear in at most
- one --bridge-interfaces. */
+/* The source interface! can only appea
On 10/06/15 10:47, Neil Jerram wrote:
On 10/06/15 10:15, Neil Jerram wrote:
On 09/06/15 22:11, Simon Kelley wrote:
A couple of (very small quibbles)
-/* The source interface can only appear in at most
- one --bridge-interfaces. */
+
On 09/06/15 22:11, Simon Kelley wrote:
On 08/06/15 12:37, Neil Jerram wrote:
I'm sorry, this is a really old thread that I'm only just now getting
back to.
As a reminder, it's a set of patches that extend the semantics of
--bridge-interface to DHCPv6 and router advertisements. Our last
exchang
On 08/06/15 12:37, Neil Jerram wrote:
> I'm sorry, this is a really old thread that I'm only just now getting
> back to.
>
> As a reminder, it's a set of patches that extend the semantics of
> --bridge-interface to DHCPv6 and router advertisements. Our last
> exchange (as below) was about fixing
I'm sorry, this is a really old thread that I'm only just now getting
back to.
As a reminder, it's a set of patches that extend the semantics of
--bridge-interface to DHCPv6 and router advertisements. Our last
exchange (as below) was about fixing a subtle difference in behaviour
between the
On 07/10/14 18:28, Neil Jerram wrote:
>> On 03/10/14 16:54, Neil Jerram wrote:
>
>>> I'd like to propose the attached patches, which extend the aliasing
>>> concept of the --bridge-interface option to DHCPv6 and Router
>>> Advertisement processing. [...]
>>
>> A query: the semantics you've provid
> On 03/10/14 16:54, Neil Jerram wrote:
> > I'd like to propose the attached patches, which extend the aliasing
> > concept of the --bridge-interface option to DHCPv6 and Router
> > Advertisement processing. [...]
>
> A query: the semantics you've provided for DHCPv6 are subtly different
> than
On 03/10/14 16:54, Neil Jerram wrote:
> Hi all,
>
> I'd like to propose the attached patches, which extend the aliasing
> concept of the --bridge-interface option to DHCPv6 and Router
> Advertisement processing. Prior to these patches, the effect of the
> --bridge-interface option is limited to D
Hi all,
I'd like to propose the attached patches, which extend the aliasing
concept of the --bridge-interface option to DHCPv6 and Router
Advertisement processing. Prior to these patches, the effect of the
--bridge-interface option is limited to DHCPv4. I think it's a
natural extension for it to
17 matches
Mail list logo
