Skip to contentSkip to conversation

.gitignore update

PATCH In review Alexey Dobriyan 2 participants 3 messages Jul 26, 2007 – Jul 30, 2007

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 .gitignore update

Somehow I ended up with the following in tree:

	$ git status
		...
	# Untracked files:
	#   (use "git add <file>..." to include in what will be committed)
	#
	#       fs/proc/root.o.FuMxJQ
	#       net/ipv4/tcp_minisocks.o.geCDYR

These are presumably temporary gcc files, which aren't interesting.

---

 .gitignore |    1 +
 1 file changed, 1 insertion(+)
.gitignore +1 -0
@@ -7,6 +7,7 @@
 #
 .*
 *.o
+*.o.*
 *.a
 *.s
 *.ko
#1 lore raw
Quoted 11 lines · Alexey Dobriyan

Somehow I ended up with the following in tree:

	$ git status
		...
	# Untracked files:
	#   (use "git add <file>..." to include in what will be committed)
	#
	#       fs/proc/root.o.FuMxJQ
	#       net/ipv4/tcp_minisocks.o.geCDYR
Quoted 1 line

These are presumably temporary gcc files, which aren't interesting.

But they should not be there by default! Or are they? Looks like an interrupted assembler stage or so. So I do not think *.o.* should be added.

Jan

#2 lore raw
Quoted 13 lines · Jan Engelhardt
Quoted 11 lines · Alexey Dobriyan

Somehow I ended up with the following in tree:

	$ git status
		...
	# Untracked files:
	#   (use "git add <file>..." to include in what will be committed)
	#
	#       fs/proc/root.o.FuMxJQ
	#       net/ipv4/tcp_minisocks.o.geCDYR
Quoted 3 lines
Quoted 1 line

These are presumably temporary gcc files, which aren't interesting.

But they should not be there by default! Or are they?

Who knows. I straced a bit but rename(2) seems to not happen. However, this is not the first time I see them, and yes, box is frequently rebooted hard way.

Quoted 1 line

Looks like an interrupted assembler stage or so.

These *.o.* are normal but truncated corresponding *.o files.

Quoted 1 line

So I do not think *.o.* should be added.