<br><br><div class="gmail_quote">On Tue, Apr 26, 2011 at 6:35 AM, Ivan Lazar Miljenovic <span dir="ltr"><<a href="mailto:ivan.miljenovic@gmail.com">ivan.miljenovic@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 26 April 2011 13:16, Andrew Coppin <<a href="mailto:andrewcoppin@btinternet.com">andrewcoppin@btinternet.com</a>> wrote:<br>
><br>
> 2. I have no idea how to make Darcs do the thing with "hard links" (is that<br>
> even supported under Windows?) I just copy the whole folder using the normal<br>
> OS file tools.<br>
<br>
</div>darcs get path/to/other/local/repo<br></blockquote><div><br></div><div>More specifically than that. This is the workflow I follow with darcs repos. Say, that I want to get the Foo repo:</div><div>mkdir ~/repos/Foo</div>
<div>cd ~/repos/Foo</div><div>darcs get <a href="http://example.com/Foo">http://example.com/Foo</a> HEAD</div><div>darcs get HEAD feature-branch</div><div><br></div><div>Then I can send the patches from feature-branch to the official Foo repo at any time. I can also merge them back into HEAD doing a darcs pull from feature-branch to HEAD.</div>
<div><br></div><div>I think this is quite comparable to the git workflow.</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> Either way, you lose the ability to see how branches are related to each<br>
> other, which might be useful in some cases.<br>
<br>
</div>How do you "see" how git branches are related to each other?<br></blockquote><div><br></div><div>You can use gitk to see how the histories have interacted.</div><div><br></div><div>Jason</div></div>