mailing list mirror (one of many)
 help / Atom feed
From: Jonathan Nieder <>
To: Laszlo Ersek <>
Cc: public git mailing list <>,
	"Carsey, Jaben" <>,
Subject: Re: recent glob expansion breakage on Windows?
Date: Thu, 8 Mar 2018 14:03:56 -0800
Message-ID: <> (raw)
In-Reply-To: <>


Laszlo Ersek wrote:

> Jaben reports that git-send-email is suddenly failing to expand the
> "*.patch" glob for him, at the Windows CMD prompt:
> ---------
> E:\...>git send-email --suppress-cc=author --suppress-cc=self --suppress-cc=cc --suppress-cc=sob --dry-run *.patch
> No patch files specified!
> ---------
> Whereas, moving the same patch files to another subdir, and then passing
> the subdir to git-send-email, works fine.
> I seem to have found some $^O based perl code in the git tree that
> expands the glob manually (in place of the shell) on Windows -- however,
> that code looks ancient ^W very stable, and doesn't seem to explain the
> sudden breakage.
> Is it possible that a separate perl update on Jaben's Windows box is
> causing this? Or does the breakage look consistent with a recent git change?
> Has anyone else reported something similar recently?

This reminds me of
There, Johannes Schindelin writes (about a different command):

| This is expected because neither PowerShell nor cmd.exe nor git.exe
| expand wildcards. Those examples you found were written with a shell
| in mind, and the shell expands wildcards (hence Git does not think
| it needs to).

That may or may not also apply to send-email.  In what version did it


> Thanks (and sorry about the noise; this list might not be the best place
> to ask)!
> Laszlo

  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 21:02 Laszlo Ersek
2018-03-08 22:03 ` Jonathan Nieder [this message]
2018-03-09  9:41   ` Laszlo Ersek
2018-03-13 23:12     ` Carsey, Jaben

Reply instructions:

You may reply publically 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:

  List information:

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

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:
       or Tor2web:

AGPL code for this site: git clone public-inbox