Ben, I've been having two of the three SoK students I'm helping this winter use clones so far (the other one hasn't gotten to that point yet) for the following reasons.
1. A scratch repo isn't available to push to since the original repo had audit hook exceptions, so pushing to a scratch repo requires these same audit hook exceptions to push the initial repo/branch. 2. The students typically change their commits quite often after review (sometimes many times to finally get it right) and force pushing isn't permitted, but is on clones. I guess 2 could be solved with more commits rather than changing the commits though. BR, Jeremy On Mon, Dec 29, 2014 at 4:35 AM, Sven Brauch <svenbra...@googlemail.com> wrote: > > Noooo not scratch repos. I can see clones being useless as branches > > in the actual repos should be used instead, but I personally consider > > scratch repos a very useful thing, for example to host simple projects > > that shouldn't be part of any main/big module - they are much more > > easier to set up than proper repositories - mostly because they don't > > require manual sysadmin actions (and fileing tickets by the developer), > > it's a personal git space readily available. > +1, I also think scratch repos are useful and shouldn't be removed > mostly for the reasons Martin quoted. >
