Hi. On 21/05/13 16:36, Cyril Brulebois wrote: > [...] I think it would be safer to keep all > relevant changes into a zol (or any other appropriate name) branch,
I think so too; I did take a look at this on Github. I think it would be more accessible in Debian's repository, but ideally staged in a branch first. I noticed for example on Github a commit that was made redundant / invalidated by the next one. Also some commits have simultaneously altered whitespace and code which is hard to follow. It may be neater if the useful bits can be more neatly picked out of a branch and merged into master occasionally (e.g. at per-feature intervals). I'm glad someone is working on this though, and that we are sharing code + repository between kFreeBSD ZFS and ZoL. Also, what has happened to d-i/partman-zfs.git? The HEAD shows debian/changelog with the odd 24.tf.x versions prepended, but since then: http://anonscm.debian.org/gitweb/?p=d-i/partman-zfs.git;a=commitdiff;h=780f01b2cc1bb63b8f6f6cbc6a40ed1db03d79ef that commit showing no trace of them any more, not in the diff or context... so where did they go? Seems something got wiped out by a merge/conflict/rewrite of history... Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/519bc830.8070...@pyro.eu.org