From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: [PATCH 4/6] filter: add fprintf_filter function
Date: Sun, 12 Jan 2014 20:40:42 +0100 [thread overview]
Message-ID: <CAHmME9okHda2-gmVnxJKGuv98ct71j5Rspyj3UvF-GtTG450KA@mail.gmail.com> (raw)
In-Reply-To: <20140112193502.GS7608@serenity.lan>
On Sun, Jan 12, 2014 at 8:35 PM, John Keeping <john at keeping.me.uk> wrote:
> I'm looking at splitting up the data so there is a filter object that
> contains function pointers to implementation functions and then some
> data that is specific to to given filter type. With that change, cmd
> moves to the "exec filter" structure and is no longer accessible. I'm
> expecting some filter types to have a structured value in the config
> file that will be parsed to multiple fields which will be glued back
> together in the fprintf function for that filter type.
Compelling enough. Merging this and the subsequent ones into
jd-jk/filterinfra. I'm doing a few extra patches on top of these as we
speak. Expect an email shortly when I'm finished.
next prev parent reply other threads:[~2014-01-12 19:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 17:13 [RFC/PATCH 0/6] Preparation for more filter types john
2014-01-12 17:13 ` [PATCH 1/6] html: remove redundant htmlfd variable john
2014-01-12 19:11 ` Jason
2014-01-12 17:13 ` [PATCH 2/6] ui-snapshot: set unused cgit_filter fields to zero john
2014-01-12 17:13 ` [PATCH 3/6] filter: pass extra arguments via cgit_open_filter john
2014-01-12 19:20 ` Jason
2014-01-12 17:13 ` [PATCH 4/6] filter: add fprintf_filter function john
2014-01-12 19:23 ` Jason
2014-01-12 19:35 ` john
2014-01-12 19:40 ` Jason [this message]
2014-01-12 17:13 ` [PATCH 5/6] filter: add interface layer john
2014-01-12 17:13 ` [PATCH 6/6] filter: introduce "filter type" prefix john
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=CAHmME9okHda2-gmVnxJKGuv98ct71j5Rspyj3UvF-GtTG450KA@mail.gmail.com \
--to=cgit@lists.zx2c4.com \
/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;
as well as URLs for NNTP newsgroup(s).