All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Nicolas Pitre <nico@cam.org>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: bad git pull
Date: Sat, 17 Dec 2005 19:02:49 -0800	[thread overview]
Message-ID: <7v8xujyuna.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0512171601430.26663@localhost.localdomain> (Nicolas Pitre's message of "Sat, 17 Dec 2005 16:04:37 -0500 (EST)")

Nicolas Pitre <nico@cam.org> writes:

> One observation is that ORIG_HEAD should probably be named PREV_HEAD in 
> such context to make it more obvious what it is about.

I do not see much difference either way, but I suspect ORIG_HEAD
is pretty much well established by now.

  reply	other threads:[~2005-12-18  3:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15 23:37 bad git pull Don Zickus
2005-12-15 23:42 ` Junio C Hamano
2005-12-15 23:53   ` Junio C Hamano
2005-12-16 15:39     ` Don Zickus
2005-12-16 17:40       ` Junio C Hamano
2005-12-16 17:25     ` Carl Baldwin
2005-12-16 19:20       ` Junio C Hamano
2005-12-16 18:07     ` Morten Welinder
2005-12-16 19:21       ` Junio C Hamano
2005-12-16 22:12         ` Linus Torvalds
2005-12-17  0:37           ` Morten Welinder
2005-12-17  1:05             ` Linus Torvalds
2005-12-17  1:49               ` Junio C Hamano
2005-12-17  7:44                 ` Linus Torvalds
2005-12-17  9:28                   ` Junio C Hamano
2005-12-17 21:04                     ` Nicolas Pitre
2005-12-18  3:02                       ` Junio C Hamano [this message]
2005-12-18  4:17                         ` Nicolas Pitre
2005-12-18  6:31                           ` Linus Torvalds
2005-12-18  7:15                           ` Junio C Hamano
2005-12-18 17:16                             ` Nicolas Pitre
2005-12-17  2:19             ` 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=7v8xujyuna.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.