From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Ben Myers <bpm@sgi.com>, xfs@oss.sgi.com
Subject: Re: master branch fast-forwarded to v3.7-rc1, and corp-speak mumble
Date: Tue, 23 Oct 2012 08:32:19 -0400 [thread overview]
Message-ID: <20121023123219.GH7341@infradead.org> (raw)
In-Reply-To: <507F132B.30000@sandeen.net>
On Wed, Oct 17, 2012 at 03:20:59PM -0500, Eric Sandeen wrote:
> Dave had concerns that a regression, which, although quickly fixed, was
> cited as the reason for missing a merge window.
>
> This concerns me too, because it's not just SGI's timetables that matter
> here; others are also depending on this work getting upstream within certain
> deadlines as well.
>
> Reading back through the list, I'm alarmed that SGI wants some unspecified
> "soak time," but not upstream, for new work. There's no better place than
> an -rc1 to get soak & exposure for tested patches. Bugs get found and fixed.
> I don't think the XFS developer community needs a lecture on patch submission
> processes and quality expectations.
The best place is the for-next branch. We should aim for getting
patches in early in the window rather than last minute, which is way to
common in XFS land.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-10-23 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 15:56 master branch fast-forwarded to v3.7-rc1 Ben Myers
2012-10-17 20:20 ` master branch fast-forwarded to v3.7-rc1, and corp-speak mumble Eric Sandeen
2012-10-18 22:28 ` Ben Myers
2012-10-19 5:08 ` Dave Chinner
2012-10-22 22:23 ` Ben Myers
2012-10-23 12:32 ` Christoph Hellwig [this message]
2012-10-18 1:35 ` master branch fast-forwarded to v3.7-rc1 Dave Chinner
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=20121023123219.GH7341@infradead.org \
--to=hch@infradead.org \
--cc=bpm@sgi.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox