git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
	Git List <git@vger.kernel.org>, Jeff King <peff@peff.net>
Subject: Re: Composing git repositories
Date: Wed, 27 Mar 2013 10:16:53 -0700	[thread overview]
Message-ID: <7vobe4n4oq.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CALkWK0nARWAtC-D3UiNLccuaSwjR6meJb+Cu590N=8Ti8O7OMg@mail.gmail.com> (Ramkumar Ramachandra's message of "Wed, 27 Mar 2013 22:32:27 +0530")

Ramkumar Ramachandra <artagnon@gmail.com> writes:

> Sorry, I'm deviating.  I learnt why you think the hack is necessary
> and not "too wrong".

OK.

> As I explained above, the entire design is
> asymmetric and inelegant; I think we can do much better than this.

I personally find the "explained above" part making not much sense.
Maybe others can comment on it.

  reply	other threads:[~2013-03-27 17:17 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26  7:56 Composing git repositories Ramkumar Ramachandra
2013-03-26 16:39 ` Junio C Hamano
2013-03-27 11:49   ` Ramkumar Ramachandra
2013-03-27 16:06     ` Junio C Hamano
2013-03-27 17:02       ` Ramkumar Ramachandra
2013-03-27 17:16         ` Junio C Hamano [this message]
2013-03-27 19:26         ` Jonathan Nieder
2013-03-27 20:18           ` Junio C Hamano
2013-03-27 20:42             ` Jonathan Nieder
2013-03-28 11:48             ` Ramkumar Ramachandra
2013-03-28 20:25               ` Jens Lehmann
2013-03-28 10:01           ` Ramkumar Ramachandra
2013-03-28 18:21             ` Jonathan Nieder
2013-03-28 20:17             ` Jens Lehmann
2013-03-27 23:02         ` Jens Lehmann
2013-03-28  9:16           ` Ramkumar Ramachandra
2013-03-28 20:40             ` Jens Lehmann
2013-03-31 20:34               ` Ramkumar Ramachandra
2013-03-31 22:57                 ` Jonathan Nieder
2013-04-02 17:44                   ` Ramkumar Ramachandra
2013-04-02 17:58                     ` Jeff King
2013-04-02 19:33                       ` Ramkumar Ramachandra
2013-04-02 19:56                     ` Jens Lehmann
2013-04-02 18:03                   ` Junio C Hamano
2013-04-04  6:40                     ` Junio C Hamano
2013-04-05  2:36                       ` Duy Nguyen
2013-04-05  4:53                         ` Junio C Hamano
2013-04-05  5:27                           ` Duy Nguyen
2013-04-05  7:15                             ` Jens Lehmann
2013-03-31 23:50                 ` Phil Hord
2013-04-01 12:14                   ` Jens Lehmann
2013-04-01 14:49                     ` Phil Hord
2013-04-02 18:35                     ` Ramkumar Ramachandra
2013-04-02 18:54                       ` Jonathan Nieder
2013-04-02 19:09                         ` Junio C Hamano
2013-04-02 19:11                         ` Ramkumar Ramachandra
2013-04-02 19:20                           ` Jonathan Nieder
2013-04-02 19:29                             ` Ramkumar Ramachandra
2013-04-02 19:49                               ` Ramkumar Ramachandra
2013-04-02 19:59                       ` Jens Lehmann
2013-04-01  9:50                 ` Jens Lehmann
2013-04-01  0:16 ` Seth Robertson
2013-04-02 19:19   ` Ramkumar Ramachandra

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=7vobe4n4oq.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Jens.Lehmann@web.de \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --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).