Hi,
Earlier this month I asked how best to handle two branches without a
common ancestor to sync changes from one branch to another. Initially
I did this via the grafts mechanism, but this wasn't a shared
solution, in that the graft was local to my checkout of the repository
and no one else's.
David Chanters david.chant...@googlemail.com writes:
1. I thought the replace data in .git/refs/replace was published when
I did git push so that others could use this information as a
base-point, yet it seems not to be the case. How do I publish this?
If you don't tell it what to push, the
Hi,
On 15 September 2012 18:21, Junio C Hamano gits...@pobox.com wrote:
David Chanters david.chant...@googlemail.com writes:
2. If I do publish it, are there any caveats with that? i.e.,
because the replace data will likely point to a repo which in my
working checkout I added with
Hi,
On Sat, Sep 15, 2012 at 11:49 PM, David Chanters
david.chant...@googlemail.com wrote:
Hi,
On 15 September 2012 18:21, Junio C Hamano gits...@pobox.com wrote:
Assuming that they do, pushing the replacement ref makes the
replacing object available in the pushed-into repository, so
they
4 matches
Mail list logo
