git pull opinion
- From
- Aghiles <aghilesk@gmail.com>
- Date
- Nov 5, 2007, 21:52 UTC
- Message-ID
- <3abd05a90711051352t2f6be00bsa862585abd370fb1@mail.gmail.com>
Hello,
I am not sure this is the best place to write about this. Anyway, we just switched a couple of repositories to git (from svn) here at work and one thing people find annoying is a pull into a dirty directory. Before the "stash" feature it was even worse but now we can type:
git stash
git pull
git stash applyBut isn't that something we should be able to specify to the "pull" command ? Additionally and if I am not mistakn, those commands will create "dangling" commits and blobs. So one has to execute:
git prune
Is there an "easier" way to pull into a dirty directory ? I am asking this to make sure I understand the problem and not because I find it annoying to type those 4 commands to perform a pull (although some of my colleagues do find that annoying :).
For now, I am recommanding to my colleagues to commit very often (even unfinished changes), pull, and then rebase the commits into a more meaningful commit before pushing. Which seems to be a good practice anyway,
Thank you for git,
- Aghiles.
ps; if someone is interested to hear what is the general opinion on switching to git from svn in our company, I could elaborate.