Re: Managing multiple branches in git

Alvaro Herrera wrote: <blockquote cite="mid:20090602172414.GE5845@alvh.no-ip.org" type="cite"><pre wrap="">Mark Mielke
wrote:</pre><blockquote type="cite"><pre wrap="">I am curious about why an end user would really care? CVS and SVN both

 
kept local workspace directories containing metadata. If anything, I  
find GIT the least intrusive of these three, as the .git is only in the  
top-level directory, whereas CVS and SVN like to pollute every directory.   </pre></blockquote><pre wrap="">
That's not the problem.  The problem is that it is kept in the same
directory as the checked out copy.  It would be a lot more usable if it
was possible to store it elsewhere. </pre></blockquote><br /> I'm not following. CVS and SVN both kept such directories
"inthe checked out copy." Recall the CSV/*,v files?<br /><br /> As for storing it elsewhere - if you absolute must, you
can.There is a --git-dir=GIT_DIR and --work-tree=GIT_WORK_TREE option to all git commands, and GIT_DIR / GIT_WORK_TREE
environmentvariables.<br /><br /> I just don't understand why you care. If the CVS directories didn't bug you before,
whydoes the single .git directory bug you now? I'm genuinely interested as I don't get it. :-)<br /><br /> Cheers,<br
/>mark<br /><br /><pre class="moz-signature" cols="72">-- 
 
Mark Mielke <a class="moz-txt-link-rfc2396E" href="mailto:mark@mielke.cc"><mark@mielke.cc></a>
</pre>