linux-kernel - Re: [PATCH 1/6] sched: Fix (harmless) typo 'CONFG_FAIR_GROUP

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]

Date:	Thu, 14 Jul 2011 00:35:43 +0200 (CEST)
From:	Jesper Juhl <jj@...osbits.net>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	Jiri Kosina <jkosina@...e.cz>,
	Jan H. Schönherr <schnhrr@...tu-berlin.de>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/6] sched: Fix (harmless) typo
 'CONFG_FAIR_GROUP_SCHED'

On Thu, 14 Jul 2011, Peter Zijlstra wrote:

> On Thu, 2011-07-14 at 00:07 +0200, Jiri Kosina wrote:
> > On Wed, 13 Jul 2011, Peter Zijlstra wrote:
> > 
> > > > From: =?UTF-8?q?Jan=20H=2E=20Sch=C3=B6nherr?= <schnhrr@...tu-berlin.de>
> > > 
> > > WTF am I to do with crap like that?! 
> > 
> > Peter,
> > 
> > well, umm, get a decent e-mai client? :)
> 
> its my apply scripts that create rubbish, also I'll take recommendations
> for a decent MUA, afaict they're all crap, mutt, claws, thunderbird,
> evolution all suck rocks and its basically picking the one that sucks
> least for your particular workflow.
> 
I'd recommend alpine/re-alpine - works well with all mails I receive via 
LKML and elsewhere and I never get complaints about mangled emails from 
people I send patches to (ohh and I happen to like the user interface ;-) 
- check it out.

> > git-am can also apply such thing without any problems with proper accents.
> 
> that's assuming I actually use git at that stage, I find git to be an
> utter pain to gather patches with.

Don't know your workflow, but I can tell you what I do. I just have a 
branch for patches that I'm gathering that are not yet in upstream. Apply 
any new stuff there (or cherry-pick from other branches to my queue 
branch) and then regularly rebase that branch on master (Linus' tree).
When I then want to resend some patches it's as simple as checking out my 
queue branch, doing a rebase to make sure there's no obsolete stuff in it 
and then  git format-patch  to generate mails for the patches I want to 
re-send and then read those patches in to re-alpine and send them.
To me that's not very painfull, but of course it may not match your 
workflow - just a description of mine :-) .

-- 
Jesper Juhl <jj@...osbits.net>       http://www.chaosbits.net/
Don't top-post http://www.catb.org/jargon/html/T/top-post.html
Plain text mails only, please.

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