From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Mike Frysinger <vapier@gentoo.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] libext2fs: fix return value
Date: Sat, 4 May 2013 22:52:56 -0400 [thread overview]
Message-ID: <20130505025256.GA26201@thunk.org> (raw)
In-Reply-To: <3CC14044-0A69-48EA-90C7-CF173F6A8A42@dilger.ca>
On Sat, May 04, 2013 at 08:40:21PM -0600, Andreas Dilger wrote:
> > ok, the use of "master" and "next" is weird. i was using the normal "master"
> > branch which is apparently out of date.
>
> I'd have to agree. It would be great if master was merged from maint more often so that patches would apply to either.
Sorry, I merge maint into next, but sometimes I forget to bump master
up.
Fixed now.
- Ted
prev parent reply other threads:[~2013-05-05 2:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 5:05 [PATCH] libext2fs: fix return value Mike Frysinger
2013-05-04 23:55 ` Theodore Ts'o
2013-05-05 0:58 ` Mike Frysinger
2013-05-05 2:40 ` Andreas Dilger
2013-05-05 2:52 ` Theodore Ts'o [this message]
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=20130505025256.GA26201@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=vapier@gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).