Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [PATCH] Teach 'git apply' to look at $GIT_DIR/config

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:55

Johannes Schindelin [off-list ref] writes:
On Sat, 17 Feb 2007, Junio C Hamano wrote:
quoted
Johannes Schindelin [off-list ref] writes:
quoted
quoted
I strongly disagree from my recent day-job experience. [Explains a 
convincing use case in favour of cd-up.]
Hmm. I have to think about that. But a consequence of what you suggest 
would be to disallow git-apply outside of a repository, because then you 
would introduce _another_ inconsistency (git-apply without --index would 
behave differently when inside a repo than when outside of one).
Why?  git-apply outside is like 'patch' isn't it?
So, why shouldn't it be the same inside? That's the inconsistency I am 
alluding to.
It appears that you are saying we cannot make it consistent in
both ways, and you are probably right.

I think git should cater first to git users who use git in git
repositories, which means consistency inside a git repository
between with --index and without is more important.

We can certainly teach 'git apply' without --index/--cache a new
"stay where you are" option to behave like patch (but do that
only without --index/--cache) inside a git repository for
special cases.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help