11–15 of 15 posts
I do love me some strace. It's one of those commands I talk about when asked why I prefer Linux as a developer/hacker.
Do you mean you prefer Linux over Windows? If so, then watch this talk: http://www.youtube.com/watch?v=TgmA48fILq8 Now you will prefer Solaris/BSD to Linux :)
I do love me some strace. It's one of those commands I talk about when asked why I prefer Linux as a developer/hacker.
Do you mean you prefer Linux over Windows? If so, then watch this talk: http://www.youtube.com/watch?v=TgmA48fILq8 Now you will prefer Solaris/BSD to Linux :)
To others considering watching it, the speaker is willing to indulge himself in a bit of self-absorbed wankery, but he gets most of that out of the way in the first 10 minutes, and gets down to the useful business of "here's an example problem, and here's a solution".
> git ls-tree HEAD -r |pn 4|xargs touch What's pn? I've never heard of it, I don't have it, and simple searches don't tell me anything about it. It looks like it might be a simple replacement for awk argument parsing, but I'm unsure...
> git ls-tree HEAD -r |pn 4|xargs touch What's pn? I've never heard of it, I don't have it, and simple searches don't tell me anything about it. It looks like it might be a simple replacement for awk argument parsing, but I'm unsure...
I think it's along the lines of:: cut -d' ' -F 4 That said, I'd probably try this: git ls-tree HEAD -r | sed 's/[[:space:]]\+/ /g' | cut -d' ' -f 4 Edit: Apparently there is a shorter way of that sed sequence, which brings us to: git ls-tree HEAD -r | tr -s ' ' | cut -d' ' -f 4
git ls-tree HEAD -r --name-only> touch all source code files (this step is mandatory, or else the atime won't update correctly, I don't know why, but guess it's an optimization). On a filesystem mounted with the "relatime" option, it's necessary to touch each file so that the next access is guaranteed to bump the atime. It used to be common to update the access time every time a file was accessed. That turned every read into a read+write, which is…