git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vít Ondruch" <vondruch@redhat.com>
To: git@vger.kernel.org
Subject: Pick the right default and stop warn on `git pull`
Date: Mon, 23 Nov 2020 16:13:08 +0100	[thread overview]
Message-ID: <742df4c2-2bc5-8a4b-8de1-cd5e48718398@redhat.com> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 769 bytes --]

Hi,

While I understand that the merge after `git pull` is probably not the 
best strategy (as explained in [1]), asking people to change their 
configuration to choose their default strategy with every `git pull` is 
not any better. Please select any strategy considered more appropriate 
and stop warning me. I know I could change my configuration, but I'll 
change it just if I want to differ from defaults. I don't need to be 
told that I am using wrong default. I'd like to keep my trust in Git 
upstream, but this is was not trustworthy decision IMO.

BTW, I was motivated to open this discussion by this [2] Fedora ticket.


Vít



[1] https://github.com/git/git/commit/d18c950a69

[2] https://bugzilla.redhat.com/show_bug.cgi?id=1900441


[-- Attachment #1.1.2: OpenPGP_0x0CE09EE79917B87C.asc --]
[-- Type: application/pgp-keys, Size: 61897 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

             reply	other threads:[~2020-11-23 15:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 15:13 Vít Ondruch [this message]
2020-11-23 17:59 ` Pick the right default and stop warn on `git pull` Alex Henrie
2020-11-23 19:13   ` Theodore Y. Ts'o
2020-11-23 19:40     ` Felipe Contreras
2020-11-23 20:20       ` Theodore Y. Ts'o
2020-11-23 20:34         ` Felipe Contreras
2020-11-23 21:48           ` Jeff King
2020-11-23 22:03             ` Alex Henrie
2020-11-24  0:37               ` Jeff King
2020-11-23 22:39             ` Junio C Hamano
2020-11-23 22:55             ` Felipe Contreras
2020-11-24  0:39               ` Jeff King
2020-11-24  0:57                 ` Felipe Contreras
2020-11-24  1:23                   ` Jeff King
2020-11-24  2:18                     ` Junio C Hamano
2020-11-24  2:32                       ` Jeff King
2020-11-24  3:41                         ` Felipe Contreras
2020-11-24  7:19                           ` Jeff King
2020-11-24  7:48                             ` Felipe Contreras
2020-11-24  8:07                               ` Jeff King
2020-11-24 10:35                           ` Vít Ondruch
2020-11-24 20:21                           ` Alex Henrie
2020-11-24 22:11                             ` Felipe Contreras
2020-11-24 23:23                               ` Alex Henrie
2020-11-25  0:39                                 ` Junio C Hamano
2020-11-26  1:02                                   ` Felipe Contreras
2020-11-23 19:12 ` Junio C Hamano
2020-11-23 19:37   ` Felipe Contreras
2020-11-23 19:43 ` Felipe Contreras

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=742df4c2-2bc5-8a4b-8de1-cd5e48718398@redhat.com \
    --to=vondruch@redhat.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).