All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anatolii Borodin <anatoly.borodin@gmail.com>
To: Andrew Ardill <andrew.ardill@gmail.com>
Cc: Jeff King <peff@peff.net>, Jeffrey Walton <noloader@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	Git List <git@vger.kernel.org>
Subject: Re: Please fix the useless email prompts
Date: Sun, 20 Aug 2017 23:57:17 +0200	[thread overview]
Message-ID: <CACNzp2kao+hu6a2nO=gVaLctzoDauB+xyj=cfQLUdNOXTNKQfQ@mail.gmail.com> (raw)
In-Reply-To: <CAH5451m58n8mYvt=BC_t2=EAv0HOOdAWrCHCNEPQ3NVjT174nQ@mail.gmail.com>

Hi Andrew,

On Sun, Aug 20, 2017 at 2:40 PM, Andrew Ardill <andrew.ardill@gmail.com> wrote:
> Maybe I am missing something obvious, but if that's the case then
> can't we just do the identity check when trying to make new commits,
> in which case you should be able to pull without setting your
> identity?

`git pull` is `git fetch + git merge / git rebase` in disguise, so we
should be ready if git will want to create a merge commit or do a
rebase automatically (and potentially create new commits with
`Committer` set to the current user). `git fetch` and `git clone`
alone, `git branch`, `git checkout` etc don't care about the email (as
of 2.14.1), even if `user.useConfigOnly` is set to `true`.


-- 
Mit freundlichen Grüßen,
Anatolii Borodin

  reply	other threads:[~2017-08-20 21:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19 15:10 Please fix the useless email prompts Jeffrey Walton
2017-08-19 16:36 ` Junio C Hamano
2017-08-19 18:02   ` Jeffrey Walton
2017-08-19 19:17     ` Patryk Obara
2017-08-20  9:18     ` Jeff King
2017-08-20 10:19       ` Kaartic Sivaraam
2017-08-20 12:40       ` Andrew Ardill
2017-08-20 21:57         ` Anatolii Borodin [this message]
2017-08-20 23:32           ` Andrew Ardill
2017-08-20 23:56             ` Junio C Hamano
2017-08-23 15:35               ` Jeff King
2017-08-23 17:36                 ` Junio C Hamano
2017-08-20 21:50 ` Anatolii Borodin

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='CACNzp2kao+hu6a2nO=gVaLctzoDauB+xyj=cfQLUdNOXTNKQfQ@mail.gmail.com' \
    --to=anatoly.borodin@gmail.com \
    --cc=andrew.ardill@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=noloader@gmail.com \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.