From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda3.sgi.com [192.48.176.15]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q7V8fe2P142027 for ; Fri, 31 Aug 2012 03:41:41 -0500 Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [150.101.137.141]) by cuda.sgi.com with ESMTP id o3u1Xx0BnbGQKR72 for ; Fri, 31 Aug 2012 01:42:32 -0700 (PDT) Date: Fri, 31 Aug 2012 18:42:29 +1000 From: Dave Chinner Subject: Re: [PATCH V2 00/13] xfs: remove the xfssyncd mess Message-ID: <20120831084229.GJ15292@dastard> References: <1346328017-2795-1-git-send-email-david@fromorbit.com> <20120830121516.GA285@x4> <20120830225108.GF15292@dastard> <20120831061825.GA7143@x4> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20120831061825.GA7143@x4> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Markus Trippelsdorf Cc: xfs@oss.sgi.com On Fri, Aug 31, 2012 at 08:18:25AM +0200, Markus Trippelsdorf wrote: > On 2012.08.31 at 08:51 +1000, Dave Chinner wrote: > > On Thu, Aug 30, 2012 at 02:15:16PM +0200, Markus Trippelsdorf wrote: > > > On 2012.08.30 at 22:00 +1000, Dave Chinner wrote: > > > > Version 2 of the patchset I described here: > > > > > > > > http://oss.sgi.com/archives/xfs/2012-06/msg00064.html > > > > > > > > This version has run through xfstests completely once, so it's > > > > less likely to let smoke out.... > > > > > > Is there a publicly accessible git tree available where one could pull > > > from? (This would be way easier than saving and hand-applying 13 > > > patches.) > > > > No. > > > > Instead, save all the patches to a single mbox format file, then run: > > > > $ git checkout -b umount-fix-test > > $ git am > > > > And it will apply all the patches as separate commits to the > > umount-fix-test branch. This is how I take patch sets from my inbox > > to git. You can build and testing them from there. > > Yeah. That works if you're using mbox format files. But if you're are a > Maildir user like myself you're basically screwed, because > $ git am > expects the Maildir to be *sorted* and because mails normally don't > arrive in the right order, git-am will therefore try to apply the > patches in the wrong order. (Maybe this should be reported to the git > mailing-list) > > So if there are mutt users out there who use "mbox_type=Maildir" and > know how to save a thread to a single mbox file, then please let me > know. I use mutt, and store all my mail folders in maildir format. However, I don't use mbox_type=Maildir - I simply create new maildir folders via the CLI when I need a new one. Mutt automatically recognises the directories as being in maildir format and uses it. Hence when I tag a thread and ;s to save all the tagged mail, it creates a mbox file as that is the default. That probably doesn't help you, though. However, IIRC, you can get the same result regardless of your mbox_type by piping all the tagged mail through formail and redirecting that to a file like so: ;| formail -ds > $file and that will result in $file being a mbox format file with all the tagged mail in it... Cheers, Dave. -- Dave Chinner david@fromorbit.com _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs