| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Mark Mielke <mark(at)mark(dot)mielke(dot)cc>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Managing multiple branches in git |
| Date: | 2009-06-02 21:20:20 |
| Message-ID: | 19228.1243977620@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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".
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-06-02 21:24:45 | Re: Managing multiple branches in git |
| Previous Message | Alvaro Herrera | 2009-06-02 21:08:58 | Re: Managing multiple branches in git |