From: Theodore Ts'o <tytso@mit.edu>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: lsf@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] xfstests-bld: Simplify determination of number of CPUs in build-all
Date: Sat, 29 Mar 2014 10:04:03 -0400 [thread overview]
Message-ID: <20140329140403.GB21631@thunk.org> (raw)
In-Reply-To: <CA+icZUUqDVROfgcpULciNaP=h_EJkBJHGCLNHFaNHjEEeVqV5A@mail.gmail.com>
On Sat, Mar 29, 2014 at 11:04:51AM +0100, Sedat Dilek wrote:
> >>
> >> Signed-off-by: Sedat Dilek <sedat.dilek@gmail.com>
> >
> > Thanks, applied.
> >
>
> ...and pushed?
Sorry, the conference network in Napa was a bit of a disaster. Pushed now.
> Please, document the handling of patches (and where someone can get informed).
That's a good suggestion. I'll update the documentation to include
that. (Probably on the airplane ride home.)
Cheers,
- Ted
next prev parent reply other threads:[~2014-03-29 14:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 9:03 [PATCH] xfstests-bld: Simplify determination of number of CPUs in build-all Sedat Dilek
2014-03-28 16:18 ` tytso
2014-03-29 10:04 ` Sedat Dilek
2014-03-29 14:04 ` Theodore Ts'o [this message]
2014-03-31 2:51 ` [Lsf] " Dave Chinner
2014-04-01 2:37 ` Theodore Ts'o
2014-04-01 2:37 ` Theodore Ts'o
2014-04-01 22:28 ` Dave Chinner
2014-04-01 22:28 ` Dave Chinner
2014-04-02 14:26 ` Theodore Ts'o
2014-04-03 1:14 ` Dave Chinner
2014-04-03 1:14 ` Dave Chinner
2014-04-03 10:26 ` Lukáš Czerner
2014-04-03 17:05 ` Andy Lutomirski
2014-04-03 17:35 ` Theodore Ts'o
2014-04-03 17:35 ` Theodore Ts'o
2014-04-03 17:42 ` Andy Lutomirski
2014-04-03 17:42 ` Andy Lutomirski
2014-04-03 19:06 ` Eric Sandeen
2014-04-03 19:06 ` Eric Sandeen
2014-04-03 19:21 ` Andy Lutomirski
2014-04-03 19:21 ` Andy Lutomirski
2014-04-03 21:46 ` Eric Sandeen
2014-04-03 19:30 ` Theodore Ts'o
2014-04-03 21:20 ` Dave Chinner
2014-04-03 13:16 ` Mel Gorman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140329140403.GB21631@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf@lists.linux-foundation.org \
--cc=sedat.dilek@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.