Hacker News new | past | comments | ask | show | jobs | submit login
A few git tips you didn't know about (uniqpath.com)
154 points by mtodd on July 24, 2010 | hide | past | web | favorite | 7 comments



Inaccurate -- I wrote one of those. :)

But do note that instead of this:

    git checkout -t origin/feature
You can do this:

    git checkout feature
It'll find a branch named "feature" in one of your remotes and make a local branch that tracks it.


The article uses, but does not describe pbcopy and pbpaste on os x. Feed data to pbcopy, and it goes to the clipboard:

  pwd | pbcopy # Copies the working directory to the clipboard
pbpaste outputs the clipboard contents:

  cd `pbpaste` # cd to the directory in the clipboard
(I use this to go to the same dir in a second terminal) (There's Linux equivalent called, xsel does the same.)


For Rubyists who are using Mac, these are very handy in IRB:

    # stick in .irbrc
    def copy(str)
      IO.popen('pbcopy', 'w') { |f| f << str.to_s }
    end

    def paste
      `pbpaste`
    end

    def ep
      eval(paste)
    end


I knew of pbcopy/pbpaste, but never thought of that. Great idea,

Python version (adjust to pbcopy/pbpaste if on OS X): http://gist.github.com/488852


If you're running on Windows, Vista/W7 has `clip` as an equivalent to pbcopy. One project I was working on, the sysadmin didn't give us any access to the server, so we had to instruct him to use git each time an update went through (daily). `git rev-parse HEAD | clip` was the fastest way to get the "revision your tree should be at after pulling" then and send it to him.


Good lord, the CSS on this page made me think I needed to get new glasses.


Would be nice if those that needed 1.7+ were marked so.




Registration is open for Startup School 2019. Classes start July 22nd.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: