From: Marc Strapetz <marc.strapetz@syntevo.com>
To: git@vger.kernel.org
Subject: pathspec: problems with too long command line
Date: Wed, 21 Nov 2018 10:23:34 +0100 [thread overview]
Message-ID: <c3be6eff-365b-96b8-16d2-0528612fc1fc@syntevo.com> (raw)
From our GUI client we are invoking git operations on a possibly large
set of files. This may result in pathspecs which are exceeding the
maximum command line length, especially on Windows [1] and OSX [2]. To
workaround this problem we are currently splitting up such operations by
invoking multiple git commands. This works well for some commands (like
add), but doesn't work well for others (like commit).
A possible solution could be to add another patchspec magic word which
will read paths from a file instead of command line. A similar approach
can be found in Mercurial with its "listfile:" pattern [3].
Does that sound reasonable? If so, we should be able to provide a
corresponding patch.
-Marc
[1] https://blogs.msdn.microsoft.com/oldnewthing/20031210-00/?p=41553/
[2] https://serverfault.com/questions/69430
[3] https://www.mercurial-scm.org/repo/hg/help/patterns
next reply other threads:[~2018-11-21 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 9:23 Marc Strapetz [this message]
2018-11-21 13:21 ` pathspec: problems with too long command line Jeff King
2018-11-21 13:37 ` Junio C Hamano
2018-11-21 20:56 ` Marc Strapetz
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=c3be6eff-365b-96b8-16d2-0528612fc1fc@syntevo.com \
--to=marc.strapetz@syntevo.com \
--cc=git@vger.kernel.org \
/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).