linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
	fstests@vger.kernel.org
Subject: Re: e2fsprogs, xfstests git trees pushed
Date: Tue, 16 Dec 2014 22:34:16 -0500	[thread overview]
Message-ID: <20141217033416.GV17575@thunk.org> (raw)
In-Reply-To: <20141216205319.GW24183@dastard>

On Wed, Dec 17, 2014 at 07:53:19AM +1100, Dave Chinner wrote:
> 
> And now pushed upstream, so your tree needs rebasing again.

Thanks; the workflow on my end is pretty straightforward.  "git pull
--rebase" generally does the trick without much fuss or bother.

I still have one patch left on ext4-test:

% git log --oneline master..
8a78b77 ext4/004: limit the amount of data written so test runs faster

but I'm sure that'll get picked up soon enough.

> Perhaps it would be better for kvm-xfstests to follow the upstream
> tree directly and work out some method of tagging the upstream tree
> that gives you a defined "release point" for your image builds.

There's a big fat warning on the github page that the branch is
constantly being rewound (ala linux-next) and not something should be
using for anything other than as release point.  So the current
workflow is fairly good from my perspective, and I point people at the
upstream git repo if they want to do any development.

Cheers,


	 	     	       	       	  - Ted

      reply	other threads:[~2014-12-17  3:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 19:31 e2fsprogs, xfstests git trees pushed Theodore Ts'o
2014-12-16 20:53 ` Dave Chinner
2014-12-17  3:34   ` 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=20141217033416.GV17575@thunk.org \
    --to=tytso@mit.edu \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.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).