git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Vasyl Vavrychuk <vvavrychuk@gmail.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH] Documentation/git-send-email.txt: Mention less secure app access might need to enable.
Date: Sun, 06 Sep 2020 14:52:21 -0700	[thread overview]
Message-ID: <xmqqmu224lpm.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: xmqqft85i72s.fsf@gitster.c.googlers.com

Junio C Hamano <gitster@pobox.com> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>
>> Vasyl Vavrychuk <vvavrychuk@gmail.com> writes:
>
> Another thing I forgot to say.
>
> Subject: [PATCH] Documentation/git-send-email.txt: Mention less secure app access might need to enable.
>
> Especially with grammofix s/to enable/to be enabled/ applied, the
> above is way too long as a title and would stand out like a sore
> thumb in "git shortlog --no-merges v2.28.0..v2.29.0" output.
> Something like
>
> Subject: [PATCH] send-email doc: mention less secure app access with GMail
>
> perhaps.
>
> Thanks.

Anything new on this topic?  No rush, but I'd hate to see a
basically good topic to be left in the stalled state too long.

  reply	other threads:[~2020-09-06 21:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 12:54 [PATCH] Documentation/git-send-email.txt: Mention less secure app access might need to enable Vasyl Vavrychuk
2020-08-17 17:16 ` Eric Sunshine
2020-08-29 15:39   ` Vasyl Vavrychuk
2020-08-29 18:33     ` Junio C Hamano
2020-08-29 19:29       ` Junio C Hamano
2020-09-06 21:52         ` Junio C Hamano [this message]
2020-12-22 19:58           ` Junio C Hamano
2021-01-07 11:11     ` [PATCH v3] git-send-email.txt: mention less secure app access with Gmail Denton Liu
2021-01-07 20:37       ` Eric Sunshine

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqmu224lpm.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sunshine@sunshineco.com \
    --cc=vvavrychuk@gmail.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).