Re: [PATCH] introduce git root

On 30 November 2014 at 04:38, Philip Oakley wrote: > From: "Arjun Sreedharan" >> >> This introduces `git root` which outputs the root directory >> (the directory that contains .git). >> The same can be accomplished by `git rev-parse --show-toplevel`. >> `git root` is much more intuitive and easy

[PATCH] compat: convert modes to use portable file type values

This adds simple wrapper functions around calls to stat(), fstat(), and lstat() that translate the operating system's native file type bits to those used by most operating systems. It also rewrites the S_IF* macros to the common values, so all file type processing is performed using the translated

Re: git status / git diff -C not detecting file copy

Pol, It's the same set of limitations. Git does not track renames or copies as such. It uses heuristics to compute a similarity index and then decide. All the tree stores for your copy is a file add, and that's the status you're seeing. I don't think there is any way to turn on aggressive copy det

Re: git status / git diff -C not detecting file copy

Hi Bryan, OK that explains the behavior of git diff, but what about git status? The doc implies it should be able to detect copies in the index / staging area since it has a "C" state. - Pol On Sun, Nov 30, 2014 at 10:03 AM, Bryan Turner wrote: > Pol, > > By default, -C only finds copies when t

Re: git status / git diff -C not detecting file copy

Pol, By default, -C only finds copies when the source file was also modified in the same commit. Since you did not modify hello.txt in the same commit where you copied it to copied.txt, it will not be considered. If you pass -C -C (twice), or use --find-copies-harder, Git will consider all files

git status / git diff -C not detecting file copy

Hi, The documentation for git status at http://git-scm.com/docs/git-status implies that it should be able to detect both renames and copies (with the R and C states). The command git diff -C should do it as well. However I can't get either to detect copies in this simple test case - what is happe

Re: [PATCH] introduce git root

From: "Arjun Sreedharan" This introduces `git root` which outputs the root directory (the directory that contains .git). The same can be accomplished by `git rev-parse --show-toplevel`. `git root` is much more intuitive and easy to remember. All it does is set the arguments for rev-parse This

[PATCH] introduce git root

This introduces `git root` which outputs the root directory (the directory that contains .git). The same can be accomplished by `git rev-parse --show-toplevel`. `git root` is much more intuitive and easy to remember. All it does is set the arguments for rev-parse Signed-off-by: Arjun Sreedharan -

Re: [RFC] [PATCH] remote: add new --fetch option for set-url

From: "Peter Wu" Ok, I will make a clear note about the default (without --only) behavior having weird behavior for historical reasons. Are you really OK with --only=both? It sounds a bit odd (mathematically speaking it is correct as fetch and push are both partitions that form the whole set