On 20. 3. 2015 21:30, Warren Young wrote: > On Mar 19, 2015, at 9:27 PM, Richard Hipp <d...@sqlite.org> wrote: >> >> There is no documentation because I could not conceive of wanting to >> use a VCS in any other way. > > It’s been several years since Git emerged as top dog in the DVCS race, so > there must be a significant number of people who have used nothing else. > They’re going to be trained to think that stash-and-switch is the only way.
Hi. Not sure if this wasn't mentioned on purpose, but git kinda sorta supports multiple checkouts, depending on how hard you want to stick to the definition. First, there's the option of cloning the repository locally, which will result in two working copies you can work on independently. Maybe too independently, as each working copy has its own repo. If you want to see some structure there, you can keep one clone as a bare repo and consider it primary. Git should use hard links for local cloning, so the operation shouldn't be slower than with Fossil. Second, there's git-new-workdir. I have not used it, but it seems to exist exactly for this use case. <https://github.com/git/git/blob/master/contrib/workdir/git-new-workdir> -- David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
