From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>,
Roland Hieber <r.hieber@pengutronix.de>
Subject: Re: [ptxdist] [PATCH v2 3/5] nftables: Fix Vim modelines
Date: Tue, 10 Apr 2018 11:02:53 +0200 [thread overview]
Message-ID: <3700604.mWpX64NbRg@ada> (raw)
In-Reply-To: <20180410084732.qcu4hl5xsomkpwdn@pengutronix.de>
Hei hei,
Am Dienstag, 10. April 2018, 10:47:32 CEST schrieb Michael Olbrich:
> No. If we change the modelines, then we do this for all files. I don't
> really care about this. Feel free to start a discussion to figure out the
> 'correct' modelines. I see several different ones right now. Then we can
> script this to change all files including templates.
Well, it annoys me a litte, let's say I care. ;-)
I tried starting a discussion back in 2017 [1], maybe we just start over again
and I throw in my needs for that?
Greets
Alex
[1] https://www.mail-archive.com/ptxdist@pengutronix.de/msg11771.html
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-04-10 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 9:07 [ptxdist] [PATCH v2 0/5] netfilter: Upgrades and autostart Alexander Dahl
2018-04-06 9:07 ` [ptxdist] [PATCH v2 1/5] libnftnl: Upgrade from 1.0.6 to 1.0.9 Alexander Dahl
2018-04-06 9:07 ` [ptxdist] [PATCH v2 2/5] nftables: Upgrade from v0.6 to v0.8.3 Alexander Dahl
2018-04-06 9:48 ` Alexander Dahl
2018-04-06 9:07 ` [ptxdist] [PATCH v2 3/5] nftables: Fix Vim modelines Alexander Dahl
2018-04-10 8:47 ` Michael Olbrich
2018-04-10 9:02 ` Alexander Dahl [this message]
2018-04-10 14:03 ` Michael Olbrich
2018-04-06 9:07 ` [ptxdist] [PATCH v2 4/5] nftables: Add example config file Alexander Dahl
2018-04-06 9:07 ` [ptxdist] [PATCH v2 5/5] nftables: Add bbinit startscript Alexander Dahl
2018-04-09 8:30 ` Michael Olbrich
2018-04-09 9:16 ` Alexander Dahl
2018-04-10 6:57 ` Alexander Dahl
2018-04-10 8:42 ` Michael Olbrich
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=3700604.mWpX64NbRg@ada \
--to=ada@thorsis.com \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=r.hieber@pengutronix.de \
/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