From: Aditya Garg <gargaditya08@live.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
Eric Sunshine <sunshine@sunshineco.com>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
Ben Knoble <ben.knoble@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH] docs: explain how to use `git imap-send --list` command to get a list of available folders
Date: Tue, 22 Jul 2025 16:35:05 +0000 [thread overview]
Message-ID: <06DB740D-4A94-4588-8666-DEF29C46538C@live.com> (raw)
In-Reply-To: <xmqqfreotegx.fsf@gitster.g>
> On 22 Jul 2025, at 9:17 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> Aditya Garg <gargaditya08@live.com> writes:
>
>> The output `git imap-send --list` command can be a bit confusing for new
>> users since the IMAP LIST command output is very verbose. Help such users
>> to analyse the same by using an example output.
>
> The documentation added by 067a91b0 (imap-send: add ability to list
> the available folders, 2025-06-20) is overly insufficient, so let's
> queue this update on top of it.
>
> But I am not sure if "very verbose" is a cause for worry. I would
> agree if the argument were that it is not very friendly to end-users
> to throw raw IMAP protocol messages at them. But it is what needs
> to be fixed in the implementation, not papered over with
> documentation.
It’s not really easy to make it more user friendly. Regex with C is a PITA for me, and different email servers might have slightly different ways to express the same output. Also, this much verbosity gives necessary details to locate subfolders, tags etc.
prev parent reply other threads:[~2025-07-22 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 11:43 [PATCH] docs: explain how to use `git imap-send --list` command to get a list of available folders Aditya Garg
2025-07-22 11:48 ` [PATCH v2] " Aditya Garg
2025-07-22 15:47 ` [PATCH] " Junio C Hamano
2025-07-22 16:35 ` Aditya Garg [this message]
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=06DB740D-4A94-4588-8666-DEF29C46538C@live.com \
--to=gargaditya08@live.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.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