git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: use of temporary refs in resolve
Date: Tue, 09 Aug 2005 10:07:25 +0100	[thread overview]
Message-ID: <tnxmznr32cy.fsf@arm.com> (raw)
In-Reply-To: <7v1x53zuyv.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Mon, 08 Aug 2005 19:48:24 -0700")

Junio C Hamano <junkio@cox.net> wrote:
> 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?

I shouldn't have said anything :-).

StGIT implements a pull command which pops all the patches from the
stack, pulls the latest remote changes and pushes the patches back. I
was lazy and I implemented the pulling stage by simply calling
git-fetch-script and advancing the base of the stack to the value in
FETCH_HEAD. I didn't have any special reason for this and I could have
used git-pull-script instead and not rely on the presence of
FETCH_HEAD. I don't have any preference here.

> Could you explain how you currently do things, and
> what changes I will be making would break the way you currently
> do things please?

If you plan to implement multiple values in FETCH_HEAD, StGIT won't be
able to use this since it doesn't do any merging for the base of the
stack. As I said above, this is not a problem and I was probably wrong
when decided to use git-fetch-script directly and not git-pull-script.

Please let me know if you need more info.

-- 
Catalin

  reply	other threads:[~2005-08-09  9:08 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
2005-08-09  9:07         ` Catalin Marinas [this message]
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=tnxmznr32cy.fsf@arm.com \
    --to=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --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).