Re: Managing multiple branches in git - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Managing multiple branches in git
Date
Msg-id E7E844B5-E806-4BB3-BB06-50B46A706C77@gmail.com
Whole thread Raw
In response to Re: Managing multiple branches in git  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Jun 2, 2009, at 5:20 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Robert Haas <robertmhaas@gmail.com> writes:
>> On Tue, Jun 2, 2009 at 4:09 PM, Tom Lane <tgl@sss.pgh.pa.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Managing multiple branches in git
Next
From: "David E. Wheeler"
Date:
Subject: Re: Managing multiple branches in git