linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Azat Khuzhin <a3at.mail@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Andreas Dilger <adilger@dilger.ca>,
	"open list:EXT4 FILE SYSTEM" <linux-ext4@vger.kernel.org>,
	"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH 0/5] e2fsprogs: some small cleanups and fixes for journal code
Date: Mon, 28 Jul 2014 17:53:05 +0400	[thread overview]
Message-ID: <20140728135305.GD6041@azat> (raw)
In-Reply-To: <20140728130022.GN6725@thunk.org>

On Mon, Jul 28, 2014 at 09:00:22AM -0400, Theodore Ts'o wrote:
> On Mon, Jul 28, 2014 at 12:06:19PM +0400, Azat Khuzhin wrote:
> > 
> > AFAIR it was against master.
> > Yeah massive rename will do a lot of conflicts, I've just rebased them
> > against maint without first patch and sent new patchset (v3).
> 
> Great, thanks!
> 
> For future information, if you are doing development, it's better to
> use either the maint branch (for bug fixes) or the next branch.  The
> next branch is non-rewinding, so it's safe to do development against
> it, and it's generally a few days ahead of the master branch,
> especially after I've added a large number of patches.
> 
> he basic idea is that if there are some end users which are using
> e2fsprogs' master branch, while any patches that get merged into
> "next" should be clean and safe and Bug Free(tm), that we give those
> patches a few days for people to find bugs and really obvious/stupid
> flaws that either (a) I made or that (b) I missed in my review before
> those new commits "graduate" to master.

Yeah, thanks for explanation Ted, I read about this, but I forgot to
change branch before writing patches.

Thanks,
Azat.


      reply	other threads:[~2014-07-28 13:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 14:35 [PATCH 0/5] e2fsprogs: some small cleanups and fixes for journal code Azat Khuzhin
2014-07-10 14:35 ` [PATCH 1/5] lib: add EXT2_ prefix for SUPERBLOCK_{OFFSET,SIZE} Azat Khuzhin
2014-07-10 14:35 ` [PATCH 2/5] journal: use consts instead of 1024 and add helper for journal with 1k blocksize Azat Khuzhin
2014-07-10 14:35 ` [PATCH 3/5] tune2fs: remove_journal_device(): use the correct block to find jsb Azat Khuzhin
2014-07-10 14:35 ` [PATCH 4/5] tune2fs: update journal super block when changing UUID for fs Azat Khuzhin
2014-07-10 14:35 ` [PATCH 5/5] tune2fs: update journal users while updating fs UUID (with external journal) Azat Khuzhin
2014-07-26  7:33 ` [PATCH 0/5] e2fsprogs: some small cleanups and fixes for journal code Azat Khuzhin
2014-07-26 14:31   ` Theodore Ts'o
2014-07-28  8:06     ` Azat Khuzhin
2014-07-28 13:00       ` Theodore Ts'o
2014-07-28 13:53         ` Azat Khuzhin [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=20140728135305.GD6041@azat \
    --to=a3at.mail@gmail.com \
    --cc=adilger@dilger.ca \
    --cc=darrick.wong@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).