Skip site navigation (1) Skip section navigation (2)

Re: Patch to add GIT support

From: Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, Robert Haas <robert(dot)haas(at)enterprisedb(dot)com>
Subject: Re: Patch to add GIT support
Date: 2010-06-28 06:39:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers
No objection from my end. :P
Looks good to me.

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise Postgres Company<>

On Fri, Jun 25, 2010 at 10:06 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:

> The attached patch to the build system adds the ability for version
> stamping to happen either when working in an SVN repo or GIT repo. In
> an SVN repo, it will stamp the repo version number, such as 2134:2137M
> as the current code does. In a GIT repo, it'll stamp the short version
> of the last commit hash - eg. 42c03da.
> Thanks to some^Wa lot of help from Robert Haas, it also manages to fix
> the old problem in which the build system always thought that the
> svnversion.h header had changed, thus resulting in svnversion.cpp
> being recompiled and everything being relinked, regardless of whether
> anything actually did change.
> I need to do something similar for VC++, but does anyone object to
> this? The intention is to apply it to all important branches so when
> we move to GIT, they'll just work.
> --
> Dave Page
> EnterpriseDB UK:
> The Enterprise Postgres Company
> --
> Sent via pgadmin-hackers mailing list (pgadmin-hackers(at)postgresql(dot)org)
> To make changes to your subscription:

In response to


pgadmin-hackers by date

Next:From: svnDate: 2010-06-28 12:22:01
Subject: SVN Commit by dpage: r8447 - trunk/pgadmin3
Previous:From: Erwin BrandstetterDate: 2010-06-26 11:54:26
Subject: Re: Create Table Dialog: Change Column after creation/Reorder Columns

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group