On Thu, 8 Mar 2012 17:22:14 -0700 Matt Welland <estifo...@gmail.com> wrote:
> IMHO a more viable philosophy is to use documentation and methodology > to make seamless interoperability between Windows and Unix/Linux > possible for teams that need it. Otherwise where possible and where > the code cost is not too high, independently make fossil work > perfectly on Unix and perfectly on Windows. Fossil does work perfectly both on Unix & Windows, but having those funky characters (space included) in a filenames which are meant to be kept under DVCS is *bad practice* both on Unix & Windows. As I wrote earlier, not being able to have space in a tag name is much severe limitation, but I do not hear many people complain about (g)it. If Bob Coder is moving his development team off of AntiquatedSCM they should be prepare to have some migration issues with *any* DVCS they choose and we would like to hear more about that AntiquatedSCM... Sincerely, Gour -- One who is able to withdraw his senses from sense objects, as the tortoise draws its limbs within the shell, is firmly fixed in perfect consciousness. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
signature.asc
Description: PGP signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
