ing else clever I am not aware of.
Thanks so much for your assistance.
On Tue, Apr 14, 2015 at 1:17 PM, Junio C Hamano wrote:
> Matthew Rothenberg writes:
>
>> - what is the expected PATH modification behavior for subprocesses of
>> git-hooks? Is this documented anywhere?
&
Using git 2.3.5 (on darwin, installed via homebrew), when executing a
script via the commit-msg githook, the following gets *prepended* to
the $PATH for the subprocess:
/usr/local/Cellar/git/2.3.5/libexec/git-core:/usr/local/Cellar/git/2.3.5/libexec/git-core:/usr/local/bin:{rest
of path...}
I
On Mon, Mar 9, 2015 at 2:49 AM, Jeff King wrote:
> $ git init
> $ seq 1 1000 >file && git add file && git commit -m base
> $ mv file other
> $ echo foo >file
> $ git add .
> $ git status --short
> M file
> C file -> other
Fantastic, I am able to replicate with these steps and wi
On Sun, Mar 8, 2015 at 4:14 AM, Junio C Hamano wrote:
> I think this is how -z was designed to be used, and if that isn't
> clear, then the documentation must be updated to clarify. Rename
> and Copy are the only ones that needs two pathnames, and I suspect
> that whoever did the original descrip
I've been working on a utility that parses the output of `git status
--porcelain` as a fundamental part of its operation.
Since I would like for this tool to be as robust as possible (and
cross-platform compatibility is a goal), I am currently trying to
migrate it from parsing the output of `--por
5 matches
Mail list logo