* Re: e2fsprogs, xfstests git trees pushed [not found] <20141215193139.GA14298@thunk.org> @ 2014-12-16 20:53 ` Dave Chinner 2014-12-17 3:34 ` Theodore Ts'o 0 siblings, 1 reply; 2+ messages in thread From: Dave Chinner @ 2014-12-16 20:53 UTC (permalink / raw) To: Theodore Ts'o; +Cc: Ext4 Developers List, fstests [cc fstests@vger.kernel.org] On Mon, Dec 15, 2014 at 02:31:39PM -0500, Theodore Ts'o wrote: > Per our concall today, I've pushed out an updated version of e2fsprogs > to git.kernel.org. Darrick, feel free to go ahead and rebase your > patchbomb against the next branch. > > Also, I've pushed out to github > (https://github.com/tytso/xfstests.git) what I plan to be using for > testing ext4 for this development cycle. It has the latest changes > which Dave Chinner pushed out to git.kernel.org, plus three commits > which have all been sent to the mailing list for review: > > Eryu Guan (1): > generic/299: various fixes > > Theodore Ts'o (2): > common: use mke2fs -F instead of piping in yes > ext4/308,generic/324: require fallocate support And now pushed upstream, so your tree needs rebasing again. 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. Cheers, Dave. -- Dave Chinner david@fromorbit.com ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: e2fsprogs, xfstests git trees pushed 2014-12-16 20:53 ` e2fsprogs, xfstests git trees pushed Dave Chinner @ 2014-12-17 3:34 ` Theodore Ts'o 0 siblings, 0 replies; 2+ messages in thread From: Theodore Ts'o @ 2014-12-17 3:34 UTC (permalink / raw) To: Dave Chinner; +Cc: Ext4 Developers List, fstests 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-12-17 3:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20141215193139.GA14298@thunk.org>
2014-12-16 20:53 ` e2fsprogs, xfstests git trees pushed Dave Chinner
2014-12-17 3:34 ` Theodore Ts'o
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox