From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Stefan Ring <stefanrin@gmail.com>, linux-xfs@vger.kernel.org
Subject: Re: Collecting aged XFS profiles
Date: Fri, 21 Jul 2017 08:27:43 +1000 [thread overview]
Message-ID: <20170720222743.GV17762@dastard> (raw)
In-Reply-To: <a7d9b022-4328-995c-845e-abc59e5fd038@sandeen.net>
On Thu, Jul 20, 2017 at 09:24:58AM -0500, Eric Sandeen wrote:
> On 07/19/2017 11:38 PM, Dave Chinner wrote:
> > On Wed, Jul 19, 2017 at 10:55:23PM -0500, Eric Sandeen wrote:
> > FWIW, people building from the git tree are probably using the
> > master branch (v4.11.0), not the for-next branch. I used to stage
> > all the -rcX releases in the master branch, which was why I was
> > confused by this at first. Never mind, I'll update my scripts that
> > haven't been pulling the xfsprogs for-next branch from kernel.org...
>
> yeah, I was doing that when I was new to the maintainer game, for-next
> was rebasable and more forgiving. Maybe I should change that back.
Yeah, for-next is more forgiving, but if you are tagging stuff for
releases (even -rc) then it probably should have been merged back
into the master branch and then tagged. I've always worked under the
assumption that -rc releases are "stable" release points because you
are asking the wider public to use and test the release....
i.e. If stuff needs to be undone after a -rc release then we should
use reverts that explain why something was undone - rebasing the
entire dev branch to remove the problem from recorded history means
we can't easily find out why that thing caused problems years down
the track.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2017-07-20 22:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 0:11 Collecting aged XFS profiles Saurabh Kadekodi
2017-07-16 2:57 ` Eric Sandeen
2017-07-17 19:00 ` Stefan Ring
2017-07-17 23:48 ` Dave Chinner
2017-07-18 5:45 ` Saurabh Kadekodi
2017-07-19 7:59 ` Stefan Ring
2017-07-19 15:20 ` Eric Sandeen
2017-07-19 21:08 ` Stefan Ring
2017-07-19 22:00 ` Eric Sandeen
2017-07-20 7:52 ` Stefan Ring
2017-07-20 14:27 ` Eric Sandeen
2017-07-20 20:15 ` Stefan Ring
2017-07-20 20:21 ` Eric Sandeen
2017-07-20 3:02 ` Dave Chinner
2017-07-20 3:55 ` Eric Sandeen
2017-07-20 4:38 ` Dave Chinner
2017-07-20 14:24 ` Eric Sandeen
2017-07-20 22:27 ` Dave Chinner [this message]
2017-07-20 22:48 ` Eric Sandeen
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=20170720222743.GV17762@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=stefanrin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox