| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Michael Haggerty <mhagger(at)alum(dot)mit(dot)edu> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: git: uh-oh |
| Date: | 2010-08-18 16:36:42 |
| Message-ID: | 1282148903-sup-4514@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Michael Haggerty's message of mié ago 18 12:00:44 -0400 2010:
> 3. Run
>
> git filter-branch
>
> This rewrites the commits using any parentage changes from the grafts
> file. This changes most commits' SHA1 hashes. After this you can
> discard the .git/info/grafts file. You would then want to remove the
> original references, which were moved to "refs/original".
Hmm. If I need to do two changes in the same branch, do I need to
mention the new SHA1 for the second one (after filter-branch changes its
SHA1), or the original one? If the former, then this is going to be a
very painful process.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2010-08-18 16:58:58 | Re: git: uh-oh |
| Previous Message | Peter Eisentraut | 2010-08-18 16:29:25 | Re: Per-column collation, proof of concept |