| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 20:19:46 |
| Message-ID: | 603c8f070906021319q2bd9e4bo8b5c78ef607dd040@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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. There are so many copies of the entire project history
that you'd need an asteroid to obliterate it.
The real potential for confusion with git has to do with the need to
explicitly move commits between repositories, which is a problem that
doesn't exist in CVS or SVN where There Can Only Be One. That is not
really a problem (in fact, it's really nice) when each developer uses
a single repository, but your situation (1 developer, multiple
repositories) it's potentially quite a nuisance.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Mielke | 2009-06-02 20:30:58 | Re: Managing multiple branches in git |
| Previous Message | Robert Haas | 2009-06-02 20:13:16 | Re: Managing multiple branches in git |