All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: a@unstable.cc
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	b.a.t.m.a.n-ZwoEplunGu2X36UT3dwllkB+6BGkLq7r@public.gmane.org
Subject: Re: pull request [net]: batman-adv 20160117
Date: Sun, 17 Jan 2016 01:04:46 -0500 (EST)	[thread overview]
Message-ID: <20160117.010446.1772166493922910087.davem@davemloft.net> (raw)
In-Reply-To: <1453008281-15396-1-git-send-email-a-2CpIooy/SPIKlTDg6p0iyA@public.gmane.org>

From: Antonio Quartulli <a@unstable.cc>
Date: Sun, 17 Jan 2016 13:24:33 +0800

> here you have a bunch of patches intended for net.

Pulled, but you really need to sort something out.

You give really nice detailed, high level, descriptions of
your changes here in this pull request.  It is awesome.

But then you include other text in the merge commit I end
up getting when I pull.  I don't want that _UNLESS_ it's
exactly what you're saying here in this email and therefore
is what I would have put there anyways.

When I did this time is just concatenate them together and therefore
including both things.  But I don't want to have to even think about
this in the future.

Just let me include what you say in this email or put exactly this
text into that merge commit.

Thanks.

WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: a@unstable.cc
Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] pull request [net]: batman-adv 20160117
Date: Sun, 17 Jan 2016 01:04:46 -0500 (EST)	[thread overview]
Message-ID: <20160117.010446.1772166493922910087.davem@davemloft.net> (raw)
In-Reply-To: <1453008281-15396-1-git-send-email-a@unstable.cc>

From: Antonio Quartulli <a@unstable.cc>
Date: Sun, 17 Jan 2016 13:24:33 +0800

> here you have a bunch of patches intended for net.

Pulled, but you really need to sort something out.

You give really nice detailed, high level, descriptions of
your changes here in this pull request.  It is awesome.

But then you include other text in the merge commit I end
up getting when I pull.  I don't want that _UNLESS_ it's
exactly what you're saying here in this email and therefore
is what I would have put there anyways.

When I did this time is just concatenate them together and therefore
including both things.  But I don't want to have to even think about
this in the future.

Just let me include what you say in this email or put exactly this
text into that merge commit.

Thanks.

  parent reply	other threads:[~2016-01-17  6:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-17  5:24 [B.A.T.M.A.N.] pull request [net]: batman-adv 20160117 Antonio Quartulli
2016-01-17  5:24 ` [PATCH 1/8] batman-adv: Avoid recursive call_rcu for batadv_bla_claim Antonio Quartulli
2016-01-17  5:24 ` [B.A.T.M.A.N.] " Antonio Quartulli
2016-01-17  5:24 ` [B.A.T.M.A.N.] [PATCH 2/8] batman-adv: Avoid recursive call_rcu for batadv_nc_node Antonio Quartulli
2016-01-17  5:24 ` Antonio Quartulli
2016-01-17  5:24 ` [PATCH 3/8] batman-adv: Drop immediate batadv_orig_ifinfo free function Antonio Quartulli
2016-01-17  5:24 ` [B.A.T.M.A.N.] " Antonio Quartulli
2016-01-17  5:24 ` [B.A.T.M.A.N.] [PATCH 4/8] batman-adv: Drop immediate batadv_neigh_node " Antonio Quartulli
2016-01-17  5:24 ` Antonio Quartulli
2016-01-17  5:24 ` [B.A.T.M.A.N.] [PATCH 5/8] batman-adv: Drop immediate batadv_hardif_neigh_node " Antonio Quartulli
2016-01-17  5:24 ` Antonio Quartulli
2016-01-17  5:24 ` [PATCH 6/8] batman-adv: Drop immediate neigh_ifinfo " Antonio Quartulli
2016-01-17  5:24   ` [B.A.T.M.A.N.] " Antonio Quartulli
2016-01-17  5:24 ` [PATCH 7/8] batman-adv: Drop immediate batadv_hard_iface " Antonio Quartulli
2016-01-17  5:24   ` [B.A.T.M.A.N.] " Antonio Quartulli
2016-01-17  5:24 ` [PATCH 8/8] batman-adv: Drop immediate orig_node " Antonio Quartulli
2016-01-17  5:24   ` [B.A.T.M.A.N.] " Antonio Quartulli
     [not found] ` <1453008281-15396-1-git-send-email-a-2CpIooy/SPIKlTDg6p0iyA@public.gmane.org>
2016-01-17  6:04   ` David Miller [this message]
2016-01-17  6:04     ` [B.A.T.M.A.N.] pull request [net]: batman-adv 20160117 David Miller
2016-01-17  6:12     ` Antonio Quartulli
     [not found]       ` <569B30D0.2040406-2CpIooy/SPIKlTDg6p0iyA@public.gmane.org>
2016-01-17 16:39         ` David Miller
2016-01-17 16:39           ` [B.A.T.M.A.N.] " David Miller
2016-01-17  6:12     ` Antonio Quartulli
  -- strict thread matches above, loose matches on Subject: below --
2016-01-17  5:24 Antonio Quartulli

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=20160117.010446.1772166493922910087.davem@davemloft.net \
    --to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
    --cc=a@unstable.cc \
    --cc=b.a.t.m.a.n-ZwoEplunGu2X36UT3dwllkB+6BGkLq7r@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.