From: Junio C Hamano <gitster@pobox•com>
To: Tuncer Ayaz <tuncer.ayaz@gmail•com>
Cc: git@vger•kernel.org, Josh Triplett <josh@joshtriplett•org>
Subject: Re: co-authoring commits
Date: Wed, 17 Jun 2015 13:57:12 -0700 [thread overview]
Message-ID: <xmqqmvzy59zr.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAOvwQ4j2bjR1jnLVyZbw1OCE=xQxbCEFGKcK1bpuv1K3s_Y2EQ@mail.gmail.com> (Tuncer Ayaz's message of "Wed, 17 Jun 2015 22:26:32 +0200")
Tuncer Ayaz <tuncer.ayaz@gmail•com> writes:
> On Wed, Jun 17, 2015 at 9:58 PM, Junio C Hamano wrote:
>> Tuncer Ayaz <tuncer.ayaz@gmail•com> writes:
>>
>> > Is this something that breaks the design and would never be
>> > implemented,
>>
>> Yes.
>
> Junio, thanks for the quick response.
>
> I suppose things have changed since Jonathan Nieder's response in [1]
> (2010),...
I do not think there is anything changed. Jonathan was being a bit
more diplomatic and academic than I am.
"There is no reason in principle some faraway future version of Git
could" is _always_ true as a mental masturbation without taking
reality into account, aka "Sounds doable but a lot of trouble" means
"it is doable but it is dubious that it is worth doing".
next prev parent reply other threads:[~2015-06-17 20:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 19:52 co-authoring commits Tuncer Ayaz
2015-06-17 19:58 ` Junio C Hamano
2015-06-17 20:26 ` Tuncer Ayaz
2015-06-17 20:57 ` Junio C Hamano [this message]
2015-06-17 21:17 ` josh
2015-06-17 20:59 ` josh
2015-06-17 21:51 ` Junio C Hamano
2015-06-17 22:07 ` Tuncer Ayaz
2015-06-17 22:28 ` josh
2015-06-17 22:44 ` Junio C Hamano
2015-06-18 21:25 ` Jakub Narębski
2015-06-19 4:25 ` Jeff King
2015-06-19 18:02 ` Jakub Narębski
2015-06-17 22:52 ` Theodore Ts'o
2015-06-17 23:06 ` josh
2015-06-18 10:54 ` Jason Pyeron
2015-06-18 21:25 ` Tuncer Ayaz
2015-06-19 18:18 ` Jakub Narębski
2015-06-19 21:11 ` Tuncer Ayaz
2015-06-19 21:25 ` Jakub Narębski
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=xmqqmvzy59zr.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=josh@joshtriplett$(echo .)org \
--cc=tuncer.ayaz@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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