From: Sergio Callegari <sergio.callegari@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>, git@vger.kernel.org
Subject: Re: Questions about the new
Date: Tue, 13 Oct 2009 09:49:55 +0200 [thread overview]
Message-ID: <4AD43123.3060401@gmail.com> (raw)
In-Reply-To: <7v8wfge2zu.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Sergio Callegari <sergio.callegari@gmail.com> writes:
>
>
>> If I want to replace some commit X by some commit X' I merely need to
>> modify the
>> parent information of all the commits that are child of X so that they
>> pretend
>> to be child of X', or am I missing something?
>>
>
> You need to find all the commits that are child of X in the first place.
> What should happen if your colleague has such a commit in his repository
> (which you haven't fetched from yet), you enumerated all children of X
> known to you in your graft file and then you fetch from him? You need to
> enumerate all children of X again to keep the graft file up to date.
>
Ok, that is enlightening. When trying to sort out the differences,
advantages and disadvantages of
operating on arcs (grafts like) or on nodes (replacements like) I was
thinking local, rather than
distributed. Now the advantage of working on nodes is much clearer to me.
Thanks as usual for the very clear explanation.
Sergio
next prev parent reply other threads:[~2009-10-13 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 10:23 Questions about the new Sergio
2009-10-12 10:47 ` David Kågedal
2009-10-12 12:19 ` Johannes Sixt
2009-10-12 17:04 ` Sergio Callegari
2009-10-12 21:06 ` Junio C Hamano
2009-10-13 7:49 ` Sergio Callegari [this message]
2009-10-12 21:54 ` Christian Couder
2009-10-12 19:03 ` Dmitry Potapov
2009-10-13 21:33 ` Questions about the new refs/replace mechanism Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AD43123.3060401@gmail.com \
--to=sergio.callegari@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).