public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Antonio Quartulli <a@unstable.cc>
Subject: Re: [B.A.T.M.A.N.] [PATCHv2 3/4] batman-adv: Handle parent interfaces in a different netns
Date: Sat, 12 Mar 2016 08:40:57 +0100	[thread overview]
Message-ID: <1658500.AjLX8FMN5Q@sven-edge> (raw)
In-Reply-To: <3184844.OveG4HdA7g@sven-edge>

[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]

On Saturday 12 March 2016 08:34:35 Sven Eckelmann wrote:
> On Saturday 12 March 2016 12:42:36 Antonio Quartulli wrote:
> > On Sat, Mar 12, 2016 at 12:37:17AM +0100, Sven Eckelmann wrote:
> > > [1]
> > > https://git.open-mesh.org/batman-adv.git/commit/fb7b5eb8c81969dc8bea356d
> > > 0
> > > a3f0b5e72d2da49
> > 
> > Sven, what is the README there for ?
> 
> It serves different purposes. It makes sure that the directory is created by
> git on checkout even when there is no patch in the directory. It also makes
> sure that the Makefile dependency glob for compat-patches/* is at least
> generating one dependency.
> 
> But it should also be used to define the rules under which a patch in this
> directory is acceptable (of course, the rules are not yet defined - so I've
> just used a placeholder for this draft). The requirements for such a patch
> should be really high because patches tend to fail when the code or the
> surrounding code is changed. This is also the reason why I've combined the
> critical code to really small functions which avoids more patch chunks for
> more places in the code.

And maybe it should also describe how to generate patches for this directory

   git format-patch --abbrev=7 -U3 --diff-algorithm=histogram --no-signature --format=format:'From: %an <%ae>%nDate: %aD%nSubject: [PATCH] %B' -1

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-03-12  7:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-01 21:19 [B.A.T.M.A.N.] [PATCHv2 0/4] batman-adv: Add network name space support Andrew Lunn
2016-03-01 21:19 ` [B.A.T.M.A.N.] [PATCHv2 1/4] batman-adv: NETIF_F_NETNS_LOCAL feature to prevent netns moves Andrew Lunn
2016-03-13  9:29   ` Sven Eckelmann
2016-03-13 15:24     ` Andrew Lunn
2016-04-21 10:48       ` Marek Lindner
2016-03-01 21:19 ` [B.A.T.M.A.N.] [PATCHv2 2/4] batman-adv: Create batman soft interfaces within correct netns Andrew Lunn
2016-03-13 10:48   ` Sven Eckelmann
2016-03-13 15:35     ` Andrew Lunn
2016-03-01 21:19 ` [B.A.T.M.A.N.] [PATCHv2 3/4] batman-adv: Handle parent interfaces in a different netns Andrew Lunn
2016-03-04 12:35   ` Sven Eckelmann
2016-03-07 14:31     ` Andrew Lunn
2016-03-07 14:45       ` Sven Eckelmann
2016-03-11 23:37       ` Sven Eckelmann
2016-03-12  4:42         ` Antonio Quartulli
2016-03-12  7:34           ` Sven Eckelmann
2016-03-12  7:40             ` Sven Eckelmann [this message]
2016-03-07  4:21   ` Linus Lüssing
2016-03-07 13:47     ` Andrew Lunn
2016-03-13 11:02   ` Sven Eckelmann
2016-03-13 15:38     ` Andrew Lunn
2016-03-13 15:59       ` Sven Eckelmann
2016-03-01 21:19 ` [B.A.T.M.A.N.] [PATCHv2 4/4] batman-adv: debugfs: Add netns support Andrew Lunn
2016-03-07 14:21   ` Matthias Schiffer
2016-03-13  9:12     ` Sven Eckelmann
2016-03-13 15:42       ` Andrew Lunn
2016-04-18 14:41         ` Simon Wunderlich
2016-04-20  2:36           ` Andrew Lunn
2016-04-20  3:23             ` Antonio Quartulli
2016-04-20  7:02             ` Sven Eckelmann
2016-03-14 10:41       ` Matthias Schiffer

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=1658500.AjLX8FMN5Q@sven-edge \
    --to=sven@narfation.org \
    --cc=a@unstable.cc \
    --cc=b.a.t.m.a.n@lists.open-mesh.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