Re: Git conversion status
От | Robert Haas |
---|---|
Тема | Re: Git conversion status |
Дата | |
Msg-id | AANLkTikA6b5R87Yg_fzQKrTnuhaOxSUDDLACEsw+VnoF@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Git conversion status (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: Git conversion status
Re: Git conversion status |
Список | pgsql-hackers |
On Tue, Sep 21, 2010 at 1:32 PM, Alvaro Herrera <alvherre@commandprompt.com> wrote: > Excerpts from Magnus Hagander's message of lun sep 20 12:49:28 -0400 2010: > >> Committers can (and should! please test!) clone from git clone >> ssh://git@gitmaster.postgresql.org/postgresql.git. >> >> Please do *NOT* commit or push anything to this repository yet though: >> The repo is there - all the scripts to manage it are *not*. So don't >> commit until I confirm that it is. >> >> But please clone and verify the stuff we have now. > > I tried to follow the instructions on the Wiki but they didn't work. > The ones under the heading "Dependent Clone per Branch, Pushing and > Pulling From a Local Repository" that is. > > What I find is that after doing the local clone for the branch, i.e. > git clone postgresql REL9_0_STABLE > this clones only the "master" branch somehow, not the other branches; so > when I later run > git checkout REL9_0_STABLE > on that clone, it fails with this message: > > $ git checkout REL9_0_STABLE > error: pathspec 'REL9_0_STABLE' did not match any file(s) known to git. Oops. I left out a step. Fixed. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: