From: Jeff King <peff@peff.net>
To: Eric Raible <raible@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git merge remote branch says
Date: Fri, 22 May 2009 14:10:23 -0400 [thread overview]
Message-ID: <20090522181023.GA11913@coredump.intra.peff.net> (raw)
In-Reply-To: <loom.20090522T175633-762@post.gmane.org>
On Fri, May 22, 2009 at 06:08:41PM +0000, Eric Raible wrote:
> I wasn't trying to argue that a pull would be a good idea, but more
> that it's not that expensive because of the content-addressable
> nature of git's object store.
>
> And saying that is "might be costly" could be misleading to people
> who haven't groked how a commit is a commit is a commit.
OK, then I agree with you. My "costly" was just "I don't want to touch
the network if I don't have to".
-Peff
next prev parent reply other threads:[~2009-05-22 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 19:50 git merge remote branch says "Merge commit ..."? skillzero
2009-05-22 7:49 ` Jeff King
2009-05-22 17:29 ` Eric Raible
2009-05-22 17:54 ` Jeff King
2009-05-22 18:08 ` git merge remote branch says Eric Raible
2009-05-22 18:10 ` Jeff King [this message]
2009-05-22 18:30 ` git merge remote branch says "Merge commit ..."? Johannes Sixt
2009-05-23 9:17 ` Jeff King
2009-05-23 9:26 ` Junio C Hamano
2009-05-25 9:44 ` Jeff King
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=20090522181023.GA11913@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=raible@gmail.com \
/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).