From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git List <git@vger.kernel.org>,
Jens Lehmann <Jens.Lehmann@web.de>
Subject: Re: Why does 'submodule add' stage the relevant portions?
Date: Mon, 25 Mar 2013 12:13:56 -0700 [thread overview]
Message-ID: <20130325191356.GC1414@google.com> (raw)
In-Reply-To: <CALkWK0nFVOhTjY3dfcwPvjqLZgJrENo6Ha=cv-x6io_Np8FfoA@mail.gmail.com>
Ramkumar Ramachandra wrote:
> This whole "backward compatibility" thing is not black-or-white: it's
> shades of gray. Can I ask about how "backward incompatible" the other
> suggestions I listed were, just so I get a rough idea of your scale?
It depends on how important the change is and how painful the proposed
transition is.
Please don't gratuitously break things. If there is a smooth way to
accomplish the intended effect without much downside, that is
generally preferred, even if it is harder to write the code.
There are no absolutes here. It is about helping people in the
real world who never asked for such-and-such feature to avoid
suffering real breakage.
Hope that helps,
Jonathan
next prev parent reply other threads:[~2013-03-25 19:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 17:38 Why does 'submodule add' stage the relevant portions? Ramkumar Ramachandra
2013-03-25 8:35 ` Jens Lehmann
2013-03-25 8:59 ` Ramkumar Ramachandra
2013-03-25 18:43 ` Jens Lehmann
2013-03-25 19:57 ` Ramkumar Ramachandra
2013-03-25 22:57 ` Jens Lehmann
2013-03-26 7:57 ` Ramkumar Ramachandra
2013-03-26 16:57 ` Jens Lehmann
2013-03-25 17:51 ` Junio C Hamano
2013-03-25 18:02 ` Ramkumar Ramachandra
2013-03-25 18:20 ` Jonathan Nieder
2013-03-25 18:27 ` Ramkumar Ramachandra
2013-03-25 18:31 ` Junio C Hamano
2013-03-25 18:48 ` Ramkumar Ramachandra
2013-03-25 18:50 ` Jonathan Nieder
2013-03-25 19:06 ` Ramkumar Ramachandra
2013-03-25 19:13 ` Jonathan Nieder [this message]
2013-03-26 3:27 ` Duy Nguyen
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=20130325191356.GC1414@google.com \
--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).