linux-kernel - Re: linux-next: manual merge of the mvebu tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131009143727.GD5402@titan.lakedaemon.net>
Date:	Wed, 9 Oct 2013 10:37:27 -0400
From:	Jason Cooper <jason@...edaemon.net>
To:	Thierry Reding <thierry.reding@...il.com>
Cc:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: manual merge of the mvebu tree

Thierry,

On Wed, Oct 09, 2013 at 04:14:27PM +0200, Thierry Reding wrote:
> Today's linux-next merge of the mvebu tree got conflicts in

I looked in your scripts repo, and couldn't find the script you use to
send out this email thread :(  Since I can't create a patch, I'll just
ask, could you include the commit id of the branch you pulled in the
email?

eg:

Today's linux-next merge of the mvebu tree (477cdaf) got conflicts in
...

I had uploaded a new for-next branch less than 30 minutes before you
sent this out, so I wasn't sure which you were working with.  Not a big
deal, just thought I'd pass along the idea for the next time you're
tweaking your scripts.

thx,

Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/