From: Sven Eckelmann <sven@narfation.org>
To: Marek Lindner <mareklindner@neomailbox.ch>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Patchwork on open-mesh.org
Date: Sun, 28 Feb 2016 07:21:11 +0100 [thread overview]
Message-ID: <2071375.zp131KsAS3@sven-edge> (raw)
In-Reply-To: <2259545.lEtA3AoCDO@voltaire>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On Sunday 28 February 2016 12:43:27 Marek Lindner wrote:
[...]
> A few questions as to how this works:
>
> * [PATCH] MAINTAINERS: Add patchwork URL for BATMAN ADVANCED
> -> Manually marked as 'accepted' as it won't be easily detectable as
> merged. Correct ?
Correct.
> * [B.A.T.M.A.N.,2/2] batman-adv: Split batadv_iv_ogm_orig_del_if function
> -> Merged patch today but still shows up in patchwork. Should we wait for
> the auto-detection or did I do something wrong ?
I've created this patch in a way that it was better readable for you but not
detectable by the heuristic, So I've expected it to not be detected.
Marked it manually as accepted
> * [B.A.T.M.A.N.] batman-adv: Fix integer overflow in batadv_iv_ogm_calc_tq
> -> Marked as opened but has been superseded by '[B.A.T.M.A.N.] [PATCH]
> batman-adv: Fix integer overflow in batadv_iv_ogm_calc_tq' that was merged
> today ? Shall I mark as 'accepted' ?
I would have hoped that the heuristic gets this one but it didn't. Most likely
because the position changed to much (but this is just a wild guess). I've
marked it as accepted.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-02-28 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 15:39 [B.A.T.M.A.N.] Patchwork on open-mesh.org Sven Eckelmann
2016-02-21 15:40 ` [B.A.T.M.A.N.] [PATCH] MAINTAINERS: Add patchwork URL for BATMAN ADVANCED Sven Eckelmann
2016-02-27 21:10 ` Antonio Quartulli
2016-02-28 4:43 ` [B.A.T.M.A.N.] Patchwork on open-mesh.org Marek Lindner
2016-02-28 6:21 ` Sven Eckelmann [this message]
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=2071375.zp131KsAS3@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mareklindner@neomailbox.ch \
/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).