| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Git conversion status |
| Date: | 2010-09-21 18:10:48 |
| Message-ID: | 6392.1285092648@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, Sep 21, 2010 at 1:32 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
>> I tried to follow the instructions on the Wiki but they didn't work.
> Oops. I left out a step. Fixed.
While we're discussing possible errors on that page ... at the bottom of
the page under the "multiple workdirs" alternative are these recipes for
re-syncing your local checkouts:
git checkout REL9_0_STABLE
git pull
git checkout master
git reset --hard origin/master
Are the git checkout steps really needed, considering each workdir would
normally be on its target branch all the time? If so, what are they
accomplishing exactly? I don't think I've entirely internalized what
that command does.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-09-21 18:10:54 | Re: .gitignore files, take two |
| Previous Message | Heikki Linnakangas | 2010-09-21 18:06:24 | Re: moving development branch activity to new git repo |