Re: git commit -a reports untracked files after a clone

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Could be a race condition / heisenbug yep. The result of "git commit -a" differs - the directories vcs-svn and xdiff are there all the time but not the others. The only constant thing is that the command "git status" always "cleans up" everything. Another run: 

[phil@silberpfeil git]$ git --version
git version 1.7.5.1
[phil@silberpfeil tmp3]$ git clone git://git.kernel.org/pub/scm/git/git.git
Cloning into git...
remote: Counting objects: 140472, done.
remote: Compressing objects: 100% (33586/33586), done.
remote: Total 140472 (delta 105843), reused 139396 (delta 104981)
Receiving objects: 100% (140472/140472), 27.66 MiB | 642 KiB/s, done.
Resolving deltas: 100% (105843/105843), done.
[phil@silberpfeil tmp3]$ git commit --all -uall
fatal: Not a git repository (or any parent up to mount parent /Users)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[phil@silberpfeil tmp3]$ cd git
[phil@silberpfeil git]$ git commit --all -uall
# On branch master
nothing to commit (working directory clean)
[phil@silberpfeil git]$ git commit -a
# On branch master
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	t/t9601/
#	t/t9602/
#	t/t9603/
#	t/t9700/
#	t/valgrind/
#	templates/
#	vcs-svn/
#	xdiff/
nothing added to commit but untracked files present (use "git add" to track)
[phil@silberpfeil git]$ git commit -a
# On branch master
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	t/t9601/
#	t/t9602/
#	t/t9603/
#	t/t9700/
#	t/valgrind/
#	templates/
#	vcs-svn/
#	xdiff/
nothing added to commit but untracked files present (use "git add" to track)
[phil@silberpfeil git]$ git commit --all -uall
# On branch master
nothing to commit (working directory clean)
[phil@silberpfeil git]$ git commit -a
# On branch master
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	t/t9601/
#	t/t9602/
#	t/t9603/
#	t/t9700/
#	t/valgrind/
#	templates/
#	vcs-svn/
#	xdiff/
nothing added to commit but untracked files present (use "git add" to track)
[phil@silberpfeil git]$ git status
# On branch master
nothing to commit (working directory clean)
[phil@silberpfeil git]$ git commit -a
# On branch master
nothing to commit (working directory clean)
[phil@silberpfeil git]$ git commit --all -uall
# On branch master
nothing to commit (working directory clean)

Cheers,

Philipp

_______________________________________________________________

DI Philipp Metzler
Goli.at GesbR.
Dorf Rieden 7/11
A-6900 Bregenz
EU - Austria

E-Mail: phil@xxxxxxx
Skype: googol
Tel: +43 / 676 / 72 94 176
ICQ: 13950954

o www.philippmetzler.com - Softwareentwicklung und Websites mit Django und Typo3.
o www.goli.at - Ihr Speicherplatz im Netz. Messen Sie uns an unseren Daten.
o www.clickshopping.at - Wir bringen Ihre Produkte auf den Punkt.
o www.greencar.at - Elektroautos und mehr ...
_______________________________________________________________

Am 16.05.2011 um 14:08 schrieb Jeff King:

> On Mon, May 16, 2011 at 12:49:07PM +0200, Philipp Metzler wrote:
> 
>> [phil@Silberpfeil git]$ git commit -uall
>> # On branch master
>> nothing to commit (working directory clean)
> 
> Hmm, nothing. That's odd.
> 
>> [phil@Silberpfeil git]$ git commit -a
>> # On branch master
>> # Untracked files:
>> #   (use "git add <file>..." to include in what will be committed)
>> #
>> #	t/t9154/
>> #	t/t9601/
>> #	t/t9602/
>> #	t/t9603/
>> #	t/t9700/
>> #	t/valgrind/
>> #	templates/
>> #	vcs-svn/
>> #	xdiff/
>> nothing added to commit but untracked files present (use "git add" to track)
> 
> And now totally different output from before, and from the previous run.
> 
> So this is really strange. The fact that the list of directories is
> _different_ from your previous posting implies to me that it is not
> something about those particular files, but rather some weird race
> condition in the creation of those directories or the index.
> 
> But then the fact that we see them with no "-u", but don't see them with
> "-uall" implies some weird heisenbug in git's directory traversal. What
> happens if you do "git commit --all -uall"? I'd like to see if the thing
> that switches the behavior is the presence of "--all" or the absence of
> a "-u" option.
> 
> -Peff

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]