ses.
Horrible/contrived example, but demonstrates the issue:
for f in `seq 1 150`; do touch $f; (git add $f &); done
You'll get a whole bunch of:
fatal: Unable to create '/tmp/dummy/.git/index.lock': File exists.
-- Nathan
-------
ctivity.
-- Nathan
--------
Nathan Neulinger nn...@neulinger.org
Neulinger Consulting (573) 612-1412
-status to compute which files have changed without modifying an
index-file? Or are you suggesting git-status to fail if the index file
doesn't belong to the user-id who invoked the command...
Thanks,
-Santiago
--
--------
Nathan Neulinger
ks like it does
exactly what I need.
-- Nathan
On 11/22/17 10:10 AM, Santiago Torres wrote:
On Wed, Nov 22, 2017 at 09:37:09AM -0600, Nathan Neulinger wrote:
What I'm meaning is - why does it need to write the index back out to disk?
From looking at the code in builtin/commit.c it looks lik
e.path option to support the "!" syntax similar to what
aliases can do. i.e.
[include]
path = !/usr/local/bin/gen-git-env
or
[include]
cmd = /usr/local/bin/gen-git-env
-- Nathan
--------
Nathan Neulinger
config file
though as a safety measure - per-repo config could indeed be a problem.
-- Nathan
--------
Nathan Neulinger nn...@neulinger.org
Neulinger Consulting (573) 612-1412
--
To unsubscribe from this li
On 05/30/2014 02:48 PM, Junio C Hamano wrote:
Nathan Neulinger writes:
I wouldn't mind having a GIT_EMAIL envvar with the semantics you mean,
but can you say more about the use case? What's wrong with the usual
EMAIL environment variable?
EMAIL actually worked for this case f
7 matches
Mail list logo
