On 17. 07. 22 14:35, Geert Stappers via Dnsmasq-discuss wrote:
Previous-Subject: Re: [Dnsmasq-discuss] [PATCH] Create temporary leases for
DHCPOFFER actions
In-Reply-To: <c050494a-16f6-e7c4-6e5e-5b49f884a...@redhat.com>
On Fri, Jul 15, 2022 at 10:54:28PM +0200, Petr Menšík wrote:
On 7/13/22 19:20, Geert Stappers via Dnsmasq-discuss wrote:
On Fri, Jul 08, 2022 at 10:26:35PM +0200, Petr Menšík wrote:
... First two patches were already sent. I think I have sent
also following patches already, but were not able to find them.
To prevent that patches get lost,
advices the Monthly Posting to poke after eight days again.
An additional attempt to prevent that patches (and contributors) get
lost, am I now experimenting with "dnsmasq mailing list patch collection"
It is a git repository that is cloned from git://thekelleys.org.uk/dnsmasq.git
The master branch follows that repo, the other branches have patches
that I collected from this mailinglist. Currently that is the only
extra branch "y22w27", short for "year 2022, week 27". An upcoming
branch is "gcc12". I'm in need for a (short) branch name for
Create temporary leases for DHCPOFFER actions
as Previous-Subject says / suggests.
Ideas for the branch name are still welcome.
I would prefer to have a feature branches. One mailing list thread, one
branch for it. If it is named after author and number, it would be okay.
Something simple to rebase over current master and track independent
things independent.
Allows separate changes review and merging them in any order without
extra work.
Webpage https://git.sr.ht/~stappers/dnsmasqmlpc has `git clone URL`
and links for further "browsing".
Example given: https://git.sr.ht/~stappers/dnsmasqmlpc/log/y22w27
Interesting. Do you generate those by hand
or are those generated by some tool?
By hand
I have thought about a tool, which would collect patches sent from
registered people and create a pull requests on gitlab or github, which
would show their status. And if possible mark them merged automagically. But
haven't found enough free time to play with that. Sort of external pull
requests, which can be linked to bugs and tracked progress, if any.
There is 'patchwork' http://jk.ozlabs.org/projects/patchwork/
documentation is at https://patchwork.readthedocs.io/en/latest/
My estimation is that we, dnsmasq project, can live without such tool.
On the other hand it would be nice to have such tool.
Of course, Simon is the only maintainer of the repository. Whatever he
prefers is important. But I guess a tool could make changes tracking
easier without forcing Simon to change his workflow.
Groeten
Geert Stappers
P.S.
If I have missed patches, just say so.
Seems great! Thanks for the reference. I knew there has to be multiple
of projects with similar requirements. I will try to read a more about
it and if it could be enabled as addition to current patches review
workflow.
Thanks!
Petr
--
Petr Menšík
Software Engineer, RHEL
Red Hat, http://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
