| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Uriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Conflict between REL9_4_STABLE and master branch. |
| Date: | 2015-06-26 15:36:08 |
| Message-ID: | CA+TgmoZqnMn5Mqm9E5OxT23zYWc1+fFHM8WWPSO3a4yY2AHQGw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 26, 2015 at 11:22 AM, Uriy Zhuravlev
<u(dot)zhuravlev(at)postgrespro(dot)ru> wrote:
> Hello hackers.
>
> I found a strange thing. I hope it's not on purpose.
>
> Example:
> git clone git://git.postgresql.org/git/postgresql.git
> cd postgresql
> git checkout -b remotes/origin/REL9_4_STABLE
This is an awfully strange thing to do. git checkout -b creates a new
branch. Why would you create a new branch with the name
remotes/origin/EDBAS9_4_STABLE? I would just do "git checkout
REL9_4_STABLE" if that's what you want to do.
> git merge master
> MANY CONFLICTS
Well, the stuff we back-patch is going to conflict if it's been
adjusted at all. I think trying to do this is a bad idea.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-06-26 15:38:56 | Re: Hash index creation warning |
| Previous Message | Robert Haas | 2015-06-26 15:28:54 | Re: less log level for success dynamic background workers for 9.5 |