b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: 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 12:43:27 +0800	[thread overview]
Message-ID: <2259545.lEtA3AoCDO@voltaire> (raw)
In-Reply-To: <23488110.8Oiix784PY@sven-desktop>

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

On Sunday, February 21, 2016 16:39:22 Sven Eckelmann wrote:
> I've used my free time in the last week to look over the 5246 patches which 
> were sent to the B.A.T.M.A.N. mailing list. These patches were categorized
> as
> 
>  * Accepted:
>    committed to the respective repository at git.open-mesh.org
>  * Rejected:
>    Either rejected by the Maintainer(s) or withdrawn by the Author because
>    they turned out to be a bad idea
>  * RFC
>    patches which were just posted to get comments
>  * Not applicable
>    patches which were not really for a repository at git.open-mesh.org
>    (for example patches which are forwarded to net-next.git/net.git)
>  * Changes requested
>    Patch had flaws but these could be fixed but the author of the patch
> hasn't sent a new version of the patch
>  * Superseded
>    New version of the patch(set) was sent which makes the old version
> obsolete
> 
> The result can now be found at https://patchwork.open-mesh.org/

Thanks a lot for doing all this cleanup work! I doubt any mere mortal could 
have reviewed the state for 5000+ patches on a rainy weekend ..  :-)

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 ?

 * [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 ?

 * [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' ?

Thanks,
Marek

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

  parent reply	other threads:[~2016-02-28  4:43 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 ` Marek Lindner [this message]
2016-02-28  6:21   ` [B.A.T.M.A.N.] Patchwork on open-mesh.org Sven Eckelmann

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=2259545.lEtA3AoCDO@voltaire \
    --to=mareklindner@neomailbox.ch \
    --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;
as well as URLs for NNTP newsgroup(s).