From: Junio C Hamano <junkio@cox.net>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: use of temporary refs in resolve
Date: Mon, 08 Aug 2005 19:48:24 -0700 [thread overview]
Message-ID: <7v1x53zuyv.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: tnxr7d4vi5v.fsf@arm.com
Catalin Marinas <catalin.marinas@gmail.com> writes:
> OK, I wasn't that clear. Currently git-fetch-script stores the fetched
> head in the FETCH_HEAD file and git-pull-script uses this file to do
> the merging (by passing its content to git-resolve-script).
Correct. I was not planning to change that arrangement.
> Anyway, I
> can easily change StGIT to only use git-pull-script directly, without
> the intermediate fetch.
If you are happy then I should not complain ;-), and I am
certainly not complaining, but I still have this feeling that I
do not get what you are getting at. You can change it to
directly use pull without intermediate fetch, in order to cope
with what? Could you explain how you currently do things, and
what changes I will be making would break the way you currently
do things please? I need to know which detail of the current
implementation behaviour people rely on to avoid breaking
things.
next prev parent reply other threads:[~2005-08-09 2:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 19:44 use of temporary refs in resolve Junio C Hamano
2005-08-07 20:02 ` Linus Torvalds
2005-08-07 20:12 ` Junio C Hamano
2005-08-07 20:18 ` Linus Torvalds
2005-08-08 8:50 ` Catalin Marinas
2005-08-08 9:06 ` Junio C Hamano
2005-08-08 10:26 ` Catalin Marinas
2005-08-09 2:48 ` Junio C Hamano [this message]
2005-08-09 9:07 ` Catalin Marinas
2005-08-09 12:51 ` Junio C Hamano
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=7v1x53zuyv.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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).