From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
Junio C Hamano <gitster@pobox.com>,
Git List <git@vger.kernel.org>
Subject: Re: Composing git repositories
Date: Sun, 31 Mar 2013 15:57:48 -0700 [thread overview]
Message-ID: <20130331225747.GB11704@elie.Belkin> (raw)
In-Reply-To: <CALkWK0k=g3iFjmpUQA1VkuH2kZsVX1_Hpo=LZ7CuotwHz_1++g@mail.gmail.com>
Ramkumar Ramachandra wrote:
> Jens Lehmann wrote:
>> A
>> commit is the thing to record here because it *is* the perfect fit
>
> Might be, but saying that doesn't help one bit. I want to know why.
[...]
> To summarize, everyone seems to be elated with the current state of
> submodules and is vehemently defending it. I'm a little unhappy, but
> am unable to express my discontent in better prose. Let's just go
> back to writing patches, and come back to this if and when I have a
> full design.
Elated is probably not the right word. More "annoyed at being told
their work is ugly without an accompanying concrete and actionable bug
report". :)
If you are curious, at a quieter time it might be useful to ask for
pointers to the discussions that led to the current design, and folks
on the list might be glad to help.
Hope that helps,
Jonathan
next prev parent reply other threads:[~2013-03-31 22:58 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
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 [this message]
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=20130331225747.GB11704@elie.Belkin \
--to=jrnieder@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).