| From: | Michael Haggerty <mhagger(at)alum(dot)mit(dot)edu> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| 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-19 03:44:07 |
| Message-ID: | 4C6CA887.4050505@alum.mit.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> 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.
No, all SHA1s refer to the values for the *old* versions of the commits.
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Haggerty | 2010-08-19 05:00:51 | Re: git: uh-oh |
| Previous Message | KaiGai Kohei | 2010-08-19 03:36:30 | Re: security label support, part.2 |