From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Elvis Pranskevichus <el(at)prans(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: moving development branch activity to new git repo |
Date: | 2010-09-21 18:06:24 |
Message-ID: | 4C98F420.4070909@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 21/09/10 21:01, Kevin Grittner wrote:
> That still leaves me wondering how I get that out to my public git
> repo without someone resetting it on the server. Or do I have the
> ability to clean out the old stuff at:
>
> ssh://git(at)git(dot)postgresql(dot)org/users/kgrittn/postgres.git
>
> so that I can push the result of the above to it cleanly?
git push --force allows you to push the new branches over the old ones.
I don't think it will automatically garbage collect the old stuff
though, so the repository will be bloated until "git gc" runs (with
--aggressive or something, not sure). I don't know when or how that
happens in the public repos.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-21 18:10:48 | Re: Git conversion status |
Previous Message | Alvaro Herrera | 2010-09-21 18:06:02 | Re: What happened to the is_<type> family of functions proposal? |