linux-ext4 - Re: e2fsprogs, xfstests git trees pushed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 16 Dec 2014 22:34:16 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Dave Chinner <david@...morbit.com>
Cc:	Ext4 Developers List <linux-ext4@...r.kernel.org>,
	fstests@...r.kernel.org
Subject: Re: e2fsprogs, xfstests git trees pushed

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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html