Re: [script] ge: export commits as patches
Ingo Molnar <[EMAIL PROTECTED]> writes: > TREE1=$(cat-file commit 2>/dev/null $1 | head -4 | grep ^tree | cut -d' ' -f2) -- And to make it easier on your eyes, you can always rewrite stuff like that (mentioned everywhere these days :)) like: TREE1=$(cat-file commit 2>/dev/null $1 | awk '/^tree/ {print $2}' No, I'm definitely not trying to save some CPU cycles, CPU cycles are cheap, eyes are expensive! :) -- Zlatko - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
Linus Torvalds <[EMAIL PROTECTED]> writes: > Real merges have no patches taking place _anywhere_. And they take about > half a second. Doing an "update" of your tree should _literally_ boil down > to > > # > # "repo" needs to point to the repo we update from > # > rsync -avz --ignore-existing $repo/objects/. .git/objects/. I see this -avz incantation mentioned everytime when rsync is involved. But, is the -z part (compression) really necessary knowing that we're dealing with an already compressed tree? Doesn't it put additional strain on the rsync server without any benefit in this case? Or I might be too ignorant and not understand some internals well, but then... I would like to know the reason. :) Regards, -- Zlatko - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html