Re: Managing multiple branches in git

On Jun 2, 2009, at 5:20 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Tue, Jun 2, 2009 at 4:09 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Blowing away your working directory shouldn't result in loss of your
>>> entire project history.
>
>> Such an outcome could not possibly be less likely with any other
>> system than it is with git. Every single developer has a copy of
>> your
>> entire history, as does the origin server and the public mirror of
>> the
>> origin server.
>
> If it's a public project, and discounting any private branches you may
> have had. I don't see what's so unfathomable about "I'd like a clear
> separation between workspace and repository".

Well, nothing. But, logically, the risk of data loss can't be higher
just because you have more data cached locally. The problem isn't
that caching is bad; it's keeping multiple local caches coherent.

...Robert