From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [WARNING] Proposed future changes that are backward incompatible
Date: Wed, 25 Feb 2009 17:28:20 -0800 [thread overview]
Message-ID: <7vy6vux9zf.fsf@gitster.siamese.dyndns.org> (raw)
Here is a list of possible future changes to git that are backward
incompatible that are under discussion on the git mailing list.
None of them will be in the upcoming 1.6.2 release, but some of them are
likely to appear in future versions. If you think we should not introduce
some of the listed changes, here is a chance to voice your opinions and
make a convincing argument against them, so please do so. Many people
complained about the removal of many git-foo commands from user's PATH,
which was done in 1.6.0 based on user input, after it happened. You do
not want to see such a mess happen again.
Thanks.
* refuse push to update the checked out branch in a non-bare repo by default
Make "git push" into a repository to update the branch that is checked
out fail by default. You can countermand this default by setting a
configuration variable in the receiving repository.
http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007
* git-push to delete the current branch will be refused by default
Make "git push $there :$killed" to delete the branch that is pointed at
by its HEAD fail by default. You can countermand this default by
setting a configuration variable in the receiving repository.
http://thread.gmane.org/gmane.comp.version-control.git/108862/focus=108936
* git-send-email won't make deep threads by default
Many people said that by default when sending more than 2 patches the
threading git-send-email makes by default is hard to read, and they
prefer the default be one cover letter and each patch as a direct
follow-up to the cover letter. You can countermand this by setting a
configuration variable.
http://article.gmane.org/gmane.comp.version-control.git/109790
* make core.quotepath=false the default
By default, "git diff" output quotes bytes in pathnames with high bit
set, primarily to avoid corruption during e-mail based transfer. This
however is inconvenient for human readers, and also makes some poorly
written user scripts that do not unquote them fail. Change the default
so that they are not quoted (note that control characters such as HT are
always quoted). You can countermand this by setting a configuration
variable.
http://thread.gmane.org/gmane.comp.version-control.git/110033
next reply other threads:[~2009-02-26 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 1:28 Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-27 19:27 [WARNING] Proposed future changes that are backward incompatible George Spelvin
2009-02-27 19:42 ` Nicolas Pitre
2009-02-27 19:51 ` Sverre Rabbelier
2009-02-27 19:48 ` Johannes Schindelin
2009-02-27 20:54 ` Pascal Obry
2009-02-27 19:59 ` Junio C Hamano
2009-02-27 20:31 ` George Spelvin
2009-02-27 21:02 ` Junio C Hamano
2009-02-28 2:36 ` Markus Heidelberg
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=7vy6vux9zf.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).