Tom Lane wrote: <blockquote cite="mid:18639.1243975742@sss.pgh.pa.us" type="cite"><pre wrap="">Mark Mielke <a
class="moz-txt-link-rfc2396E"href="mailto:mark@mark.mielke.cc"><mark@mark.mielke.cc></a> writes:
</pre><blockquotetype="cite"><pre wrap="">As a "for example", you could have a local repo that you publish from.
Your work spaces could be from that local repo. </pre></blockquote><pre wrap="">Yes, exactly. How do I do that? My
complaintis that git fails to
provide a distinction between a repo and a workspace --- they seem
to be totally tied together. </pre></blockquote><br /> Hehe... my "for example" is a bit ambiguous. I was talking about
onecommon model I've seen under git where people have private and public repos. The private repo is where you do your
mainwork. Commits are "published" by pushing them to your public repo and making them generally available for others to
pullfrom. Under this model, your private repo could clone the public repo using --shared to keep the working copy at
minimalsize. You could have multiple private repos if this is required for your workflow. Still, it becomes a
multi-stepprocess to commit. 1) Commit to your private repo, 2) Push to your public repo, 3) If you use a centralized
repo,you need another process to push or pull the change from your public repo to the centralized repo.<br /><br />
Anotherposter referenced "git-new-workdir". It really does look like what you are looking for:<br /><br /> <a
class="moz-txt-link-freetext"
href="http://blog.nuclearsquid.com/writings/git-new-workdir">http://blog.nuclearsquid.com/writings/git-new-workdir</a><br
/><br/> If it lives up to its advertisement, it gives you a new working copy with a new index, but linked directly to
theshared repo rather than having its own repo.<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>