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] [day] [month] [year] [list]
Message-ID: <20080922121010.GA20242@elte.hu>
Date:	Mon, 22 Sep 2008 14:10:10 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Frédéric Weisbecker <fweisbec@...il.com>
Cc:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Steven Noonan <steven@...inklabs.net>
Subject: Re: [Patch 1/3] Tracing/ftrace: Make nop tracer reset previous
	entries


* Frédéric Weisbecker <fweisbec@...il.com> wrote:

> 2008/9/22 Ingo Molnar <mingo@...e.hu>:
> >
> > * KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:
> >
> >> your patch seems corrupted.
> >> please check again your e-mail client settings.
> >
> > i fixed the extra newlines up and applied the patches to
> > tip/tracing/ftrace, thanks Frédéric!
> >
> > please check Documentation/email-clients.txt about details. There were
> > two problems i saw: overlong lines in the commit description and extra
> > 'double newlines' in the patch itself. (To get around gmail limitations
> > you can send -tip patches as MIME attachments as well.)
> >
> >        Ingo
> >
> 
> Oops. I'm really sorry about that. I was pretty convinced that my
> email client was well configured.
> In the future I will first send myself the patches before any new
> submit to ensure they are not damaged...

no harm was done really, we can cope. I'd suggest you do the 
send-yourself thing once now to check that your practices are OK.

	Ingo
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ