From: Richard Weinberger <richard@nod•at>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: status of the signal-cleanup tree
Date: Mon, 13 Oct 2014 16:38:36 +0200 [thread overview]
Message-ID: <543BE3EC.9010601@nod.at> (raw)
In-Reply-To: <20141013173301.0664c8ac@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
Am 13.10.2014 um 08:33 schrieb Stephen Rothwell:
> Hi Richard,
>
> The signal-cleanup tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/rw/misc.git#signal_v4)
> has not bee touched since July and when merged into Linus' tree,
> produces no changes (same patches different commits :-(). So all it is
> doing at the moment is producing unnecessary conflicts :-(
>
> Can you clean it up, please? Or should I just remove it
> from linux-next completely.
Just remove it. The "feature" was merged.
Thanks,
//richard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-10-13 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 6:33 linux-next: status of the signal-cleanup tree Stephen Rothwell
2014-10-13 14:38 ` Richard Weinberger [this message]
2014-10-13 21:53 ` Stephen Rothwell
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=543BE3EC.9010601@nod.at \
--to=richard@nod$(echo .)at \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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