git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, Simon Brenner <olsner@gmail.com>,
	git@vger.kernel.org
Subject: Re: [RFC] deprecating and eventually removing "git relink"?
Date: Tue, 15 Nov 2011 13:48:00 +0900	[thread overview]
Message-ID: <buoehxat2in.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <7vmxbyicgg.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:
> I did not mean "it is wrong because it does not match what Miles said"
> by that. In fact, I think it is a better approach to put things in
> clients first and consolidating possible duplicates at the central one
> purely as optimization, and I do not necessarily see "write to central
> from the beginning" as a particularly good "optimization".

FWIW, this seems reasonable to me...

-Miles

-- 
Circus, n. A place where horses, ponies and elephants are permitted to see
men, women and children acting the fool.

  reply	other threads:[~2011-11-15  4:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14  0:38 [RFC] deprecating and eventually removing "git relink"? Junio C Hamano
2011-11-14  6:06 ` Miles Bader
2011-11-14  6:27   ` Junio C Hamano
2011-11-14  9:03     ` Chris Packham
2011-11-14  8:48   ` Simon Brenner
2011-11-14 10:34     ` Jeff King
2011-11-14 20:18       ` Junio C Hamano
2011-11-14 20:25         ` Jeff King
2011-11-14 22:08           ` Junio C Hamano
2011-11-15  4:48             ` Miles Bader [this message]
2011-11-21 22:09       ` Phillip Susi
2011-11-21 22:19         ` Jeff King
2011-11-22  1:58           ` Phillip Susi
2011-11-14 10:24   ` Junio C Hamano
2011-11-15  4:40     ` Miles Bader

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=buoehxat2in.fsf@dhlpc061.dev.necel.com \
    --to=miles@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=olsner@gmail.com \
    --cc=peff@peff.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).