Re: git status always modifies index?

2017-11-22 Thread Nathan Neulinger
ke 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 like it ta

Re: git status always modifies index?

2017-11-22 Thread Nathan Neulinger
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 nn...@neulinger.org

git status always modifies index?

2017-11-22 Thread Nathan Neulinger
-- Nathan -------- Nathan Neulinger nn...@neulinger.org Neulinger Consulting (573) 612-1412

Feature request - allow requesting a lock timeout

2015-12-04 Thread Nathan Neulinger
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 -------- Na

feature request - implement a GIT_AUTHOR_EMAIL equivalent, but processed BEFORE .gitconfig

2014-05-30 Thread Nathan Neulinger
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 nn...@neulinger.org Neulinger Consulting (573

Re: feature request - implement a GIT_AUTHOR_EMAIL equivalent, but processed BEFORE .gitconfig

2014-05-30 Thread Nathan Neulinger
- per-repo config could indeed be a problem. -- Nathan Nathan Neulinger nn...@neulinger.org Neulinger Consulting (573) 612-1412 -- To unsubscribe from this list: send the line unsubscribe git

Re: feature request - implement a GIT_AUTHOR_EMAIL equivalent, but processed BEFORE .gitconfig

2014-05-30 Thread Nathan Neulinger
On 05/30/2014 02:48 PM, Junio C Hamano wrote: Nathan Neulinger nn...@neulinger.org 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