xfs
[Top] [All Lists]

Re: [PATCH V2 00/13] xfs: remove the xfssyncd mess

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: [PATCH V2 00/13] xfs: remove the xfssyncd mess
From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
Date: Fri, 31 Aug 2012 11:30:16 +0200
Cc: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=simple; d=mail.ud10.udmedia.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=beta; bh=0aeP1ANt3+YUFkaEg/4ts+v1TZ EmyUj/nJHI5GJiIhs=; b=Mwp/3cORIggYI4qLS4Yd1EuO7Ge9Rm9EiOGduYCUZK jVvMOdeXrM7rj38O5EhO64hw9M4PeKHuCC8aw7ZsJ+WFwpX8rV18tiAr2U8UyBCm RnMhSYnuAsP6jQm06Ko3Or7L12oqcW6gNUWkF3XTKyNsXvhV67oqkkBf5ZZAd0ey 4=
In-reply-to: <20120831084229.GJ15292@dastard>
References: <1346328017-2795-1-git-send-email-david@xxxxxxxxxxxxx> <20120830121516.GA285@x4> <20120830225108.GF15292@dastard> <20120831061825.GA7143@x4> <20120831084229.GJ15292@dastard>
On 2012.08.31 at 18:42 +1000, Dave Chinner wrote:
> 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 <mbox file>
> > > 
> > > 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 <Maildir> 
> > 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...

After some experimentation I came up with the following:

macro index <F5> "<enter-command>set mbox_type=mbox;set confirmcreate=no;set 
sort=subject<enter>;sPatches<enter><enter-command>set mbox_type=Maildir; set 
sort=threads;set confirmcreate=yes<enter>U.<enter>"

Basically you just tag the thread (esc-t) and then hit F5 and it will save it
to a mbox file called "Patches" in your home dir.

-- 
Markus

<Prev in Thread] Current Thread [Next in Thread>