<br><div class="gmail_quote">2010/2/7 Martin Pool <span dir="ltr"><<a href="mailto:mbp@canonical.com">mbp@canonical.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It looks like the two options proposed there are:<br>
<br>
1- just skip them<br>
2- make Windows symlink-like things<br>
3- and I guess another is to write a plain file with the contents of the link<br></blockquote><div><br>I would recommend a lot of caution if/when going with option 2. Options 2 is filesystem dependent and will therefore break a lot of existing use cases. Here are a few use cases that I can think of that would be issue for me:<br>
- I frequently copy project tree on USB key to work on another machine. They tend to have FAT32 filesystem. <br>- Project tree hosted on a network drive, but using bzr from Windows (for multiplatform "simultaneous" compilation)<br>
- Few tools on Windows (are likely to) handle symlink correctly (e.g. messed up archive, project tree copy/move...). Many existing python scripts will likely have issue with symlinks too.<br>- Unless I'm mistaken, this feature is not supported by Windows XP.<br>
<br>I would tend to (slightly) prefer option 1 (skip file) over option 3 because it would result in clearer errors, as long as there is a way to see the list of skipped symblinks. On the other hand option 3 may provide a more intuitive interface to suppress/modify a symlink, but this is low priority use case comparing to being able to work on a repo with symblink. Given that you would likely not be able to test your changes one can only wonder if modifying/suppressing symlinks should be supported on Windows. <br>
<br>It is important that such branch made on Windows, when pushed, can be branched from by Unix user without issues (e.g. with symlink), generate correct patches...<br><br>Baptiste.<br></div></div>