From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: network@lists.ipfire.org
Subject: Add copy before the vpn security policies
Date: Wed, 19 Jul 2017 10:09:43 +0200 [thread overview]
Message-ID: <1500451784-5317-1-git-send-email-jonatan.schlag@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
just for clarification why I send this patch alone. I think it is easier to get this patch merged before we talk about the vpn security policies.
Make my branches easier and the emails shorter.
This method works fine and results in an error every time something goes wrong. The message should be enough o encounter what the problem is.
So hopefully this one is ok :-)
Jonatan
next reply other threads:[~2017-07-19 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 8:09 Jonatan Schlag [this message]
2017-07-19 8:09 ` [PATCH v4] util: add new function copy Jonatan Schlag
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=1500451784-5317-1-git-send-email-jonatan.schlag@ipfire.org \
--to=jonatan.schlag@ipfire.org \
--cc=network@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