git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Chris Torek <chris.torek@gmail.com>
To: "Jan “Khardix” Staněk" <khardix@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Git List" <git@vger.kernel.org>
Subject: Re: git-send-email: smtpserver in $HOME
Date: Thu, 18 Feb 2021 02:18:25 -0800	[thread overview]
Message-ID: <CAPx1Gvf1pXCp9YVQSQ1_-w3-A8qYZD7tsFV80njsXD-+Jap6Xw@mail.gmail.com> (raw)
In-Reply-To: <CAG+K25NC3H7L5TpxmR_kCvmqR8GPdCEdTt740F34ON4TWoPCpg@mail.gmail.com>

Just a small point here:

On Tue, Feb 16, 2021 at 2:17 PM Jan “Khardix” Staněk <khardix@gmail.com> wrote:
> Well, unless I'm missing something, shouldn't the tilde above be
> expanded by the shell before actually being passed as argument?

Maybe.  Some shells do and some don't:

$ echo foo=~/foo
foo=~/foo

bash$ echo foo=~/foo
foo=/home/torek/foo

for instance.

> So I actually did my homework and skimmed through the relevant RFCs
> (RFC952 and RFC1123); as it turns out, no, it cannot
> – only ASCII alphanumerics, '-' and '.' are valid characters.

Right: tilde and slash are both verboten. (Underscore is too, but
that one does get used and some programs allow it.)

Chris

  reply	other threads:[~2021-02-18 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 14:07 git-send-email: smtpserver in $HOME Jan “Khardix” Staněk
2021-02-16  2:14 ` Junio C Hamano
2021-02-16 12:49   ` Jan “Khardix” Staněk
2021-02-16 18:53     ` Junio C Hamano
2021-02-16 22:14       ` Jan “Khardix” Staněk
2021-02-18 10:18         ` Chris Torek [this message]
2021-02-18 12:57           ` Andreas Schwab
2021-02-16 15:45   ` Jeff King
2021-02-16 18:57     ` Junio C Hamano
2021-02-16 19:05       ` Jeff King
2021-02-16 19:16         ` Junio C Hamano
2021-02-16 19:23           ` Jeff King
2021-02-16 22:31         ` Jan “Khardix” Staněk

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=CAPx1Gvf1pXCp9YVQSQ1_-w3-A8qYZD7tsFV80njsXD-+Jap6Xw@mail.gmail.com \
    --to=chris.torek@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=khardix@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).