Re: [PATCH] ls-files: do not trust stat info if lstat() fails

On Thu, Apr 3, 2014 at 11:30 PM, Junio C Hamano gits...@pobox.com wrote: Duy Nguyen pclo...@gmail.com writes: On Thu, Apr 3, 2014 at 1:15 AM, Junio C Hamano gits...@pobox.com wrote: I am guessing that, even though this was discovered during the development of list-files, is a fix applicable

Re: What's cooking in git.git (Apr 2014, #01; Fri, 4)

Am 04.04.2014 22:58, schrieb Junio C Hamano: * sz/mingw-index-pack-threaded (2014-03-19) 1 commit - Enable index-pack threading in msysgit. What is the status of this topic? A failure report exists ($gmane/245170), and I am aware of Duy's $gmane/245034 but that was where the discussion

Re: What's cooking in git.git (Apr 2014, #01; Fri, 4)

On 2014-04-05 11.19, Johannes Sixt wrote: Am 04.04.2014 22:58, schrieb Junio C Hamano: * sz/mingw-index-pack-threaded (2014-03-19) 1 commit - Enable index-pack threading in msysgit. What is the status of this topic? A failure report exists ($gmane/245170), and I am aware of Duy's

[PATCH 0/2] status/commit: do not ignore staged submodules

This series fixes the problem that ignored but staged submodules do not show up in status and commit. Even though we do change default behavior here, I believe this is the Right Thing to do (and remember all interested parties in the discussion that raised this issue agreed on that [1]). [1]

[PATCH 1/2] status/commit: show staged submodules regardless of ignore config

Currently setting submodule.name.ignore and/or diff.ignoreSubmodules to all suppresses all output of submodule changes for the diff family, status and commit. For status and commit this is really confusing, as it even when the user chooses to record a new commit for an ignored submodule by adding

[PATCH 2/2] commit -m: commit staged submodules regardless of ignore config

The previous commit fixed the problem that the staged but that ignored submodules did not show up in the status output of the commit command and weren't committed afterwards either. But when commit doesn't generate the status output (e.g. when used in a script with '-m') the ignored submodule will

Çinden urun almak veya Çine urun satmak istiyorsaniz,biz buradayiz.

Sn.Yetkili, Çinden urun almak veya Çine urun satmak istiyorsaniz,biz buradayiz. Çinde kurulu firmamizla ,ozellikle avrupali firmalara cin halk cumhuriyetinden yapmakta olduklari ithalat konusunda,danismanlik ve gozetim hizmeti vermekteyiz. -Cinden yapacaginiz ithalatlarda,urunlerinizde

[PATCH] gitk: switch to patch mode when searching for line origin

If the Show origin of this line is started from tree mode, it still shows the result in tree mode, which I suppose not what user expects to see. --- gitk | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/gitk b/gitk index 90764e8..5a99350 100755 --- a/gitk +++ b/gitk @@

The fetch command should always honor remote.name.fetch

Hi all, //for tldr; see EOM I recently setup git for my team and we ran into a small annoyance. Though this may be solved with a simple alias, I decided to spend this Saturday afternoon exploring the Git source to find out how easy an actual patch could be. Unfortunately, the fix isn't trivial

Makefile: Another make command is used when going into SUBDIR perl

Package: git-1.9.0 Another make command is used in the Makefile when it enters subdir PERL. The used make command is a link in my home directory to /usr/sfw/bin/gmake. Other make commands are /usr/ccs/bin/make and /usr/xpg4/bin/make. My PATH variable has these directories in this order