From: Rob Brewer <ipfire-devel@grantura.co.uk>
To: development@lists.ipfire.org
Subject: Re: ipblacklist V2
Date: Wed, 09 Feb 2022 21:43:41 +0000 [thread overview]
Message-ID: <su1cid$ih9$1@tuscan3.grantura.co.uk> (raw)
In-Reply-To: <0845dc5e-85d2-0b25-46e5-ab7a9c604100@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]
Hi Adolf,
Thank you for the kind comments in your earlier post and I'm pleased that
ipblacklist will be incorporated into IPFire. From what I'm seeing here it
will be a very worthwhile addition. I have been looking through the Wiki
documentation for submitting patches and it looks fairly explanatory but
will probably need your help to keep me in the right place.
Adolf Belka wrote:
> Hi Rob,
>
> In your communication below about the various patches, it sounded to me
> like you are suggesting that some of the patches could be taken from the
> earlier patchset because they have not changed. My apologies if I have
> misread it.
>
I think that is correct. The majority of Tim's V2 patches can be
incorporated without changes.
> I believe that it would be better to submit a complete patchset now, where
> you include all patches, even if they haven't changed from earlier. This
> would make it much easier for tracking the status of the patches within
> patchwork and knowing what was included at a later date if looking back.
> So Tim's old patchset would be marked as superseded in patchwork and yours
> would take over and would be named as a v3 version.
>
That's OK but it'll get me a couple of days to get my head around submitting
patches and getting the correct build environment set up. I presume you
would need patches against the next development load
(git checkout -b next -t origin/next) which I will have to set up.
> Information on submitting the patches is in the wiki and if needed I can
> provide the appropriate links. If you have any questions on or problems
> with the patch submission process then just let me know.
>
Thanks Adolf, I've read some of the docs. It mostly looks OK but when I get
around to submitting patches I think I'll need some help on submitting the
Build infrastructure patches and I don't have a clue how to generate the
lang files.
It looks like the first step will be difficult but then hopefully gets
easier.
Regards
Rob
next prev parent reply other threads:[~2022-02-09 21:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 18:17 Rob Brewer
2022-02-07 10:31 ` Michael Tremer
2022-02-07 12:58 ` Rob Brewer
2022-02-09 14:38 ` Adolf Belka
2022-02-09 21:43 ` Rob Brewer [this message]
2022-02-09 22:14 ` Adolf Belka
2022-02-10 9:45 ` Michael Tremer
2022-02-09 13:23 ` Rob Brewer
2022-02-09 14:29 ` Adolf Belka
2022-02-10 9:41 ` Michael Tremer
2022-02-10 15:12 ` Rob Brewer
2022-02-10 16:48 ` Michael Tremer
2022-02-12 21:29 ` Tim FitzGeorge
2022-02-13 12:44 ` Rob Brewer
2022-02-15 12:58 ` Michael Tremer
2022-02-15 12:54 ` Michael Tremer
[not found] <ef8ac1dcde46b22207dde653d6717a95d2a737e7.camel@ipfire.org>
2022-03-01 13:13 ` Michael Tremer
2022-03-01 16:08 ` Rob Brewer
2022-03-05 18:52 ` Stefan Schantl
2022-03-05 21:46 ` Rob Brewer
2022-03-07 20:39 ` Michael Tremer
2022-03-07 22:54 ` Rob Brewer
2022-03-08 10:59 ` Rob Brewer
2022-03-08 15:45 ` Michael Tremer
2022-04-03 9:16 ` Stefan Schantl
2022-04-03 21:09 ` Rob Brewer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='su1cid$ih9$1@tuscan3.grantura.co.uk' \
--to=ipfire-devel@grantura.co.uk \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox