Think about what it would look like if a versioning system like git and a pastie had a child, and you'd probably came quite close what the folks behind the project hosting service Github let loose on the web just yesterday: Gist, a pastie that supports versioning and much more.
Archive for [<Tag: git>]
-
Github presents Gist
-
GitHub needs HTTP cloning support
One of the big disadvantages that GitHub has over for instance Gitorious is that there is no way to clone a repository over HTTP. The service is currently limited to cloning via git:// which is quite a problem if you're living behind for instance a corporate firewall.
There already is a ticket associated with this problem on GitHub's Lighthouseapp project page, where defunct wrote:
I'm going to close this until more people ask for it. We plan to start keep track of clone stats so git-daemon is actually preferable.
So please everyone, vote for this ticket.
-
About git-svn, trunk, master and everything
I guess this can be categorized as "Shooting yourself into the foot with a smile". For the last couple of days I've been working on a patch for bringing some gettext into Sphinx. First I started the work in the most recent release, just to see how hard it would be. Then I made a checkout from the SVN repo using Git in order to rewrite the patch for trunk. Everything fine, so far. Yesterday night then I wanted to go through the patch one more time before sending it through the ether and noticed something rather stupid: When checking out from SVN using git-svn, Git, for some reason, didn't make "trunk" the new master-branch, but instead, I guess, used the branch with the most recent commit.
When then moving to the "real" trunk and applying my patch, at least most of the hunks (and all the big ones) passed, so it only took me about 20 minutes to get the patch ready again.
So from now on, the first thing I will do when cloning an SVN repository is a
git reset --hard remotes/trunkas suggested by the manual (deep down in the basic examples) just to be on the safe side ;-) -
First steps with zc.buildout: Simple recipe for git
Just a small plug for a project I'm currently working on. I'm playing a little bit around with zc.buildout right now and have come to a point where I want to have dependencies not only as subversion-repository, distutils or egg. I simply end up with too many Python packages on github for not having a way to use them. So while still learning my way around buildout I wrote a little recipe to do just that: clone a git-repo and make it accessible as a part. With this you can define first of all where the repository is, and also what branch or explicit revision you want to have for your project.
There is definitely still a ton of stuff missing that you'd find in any other zc.buildout recipe, but I see this mostly as a good way to finally find my way around :-) Anyway, you can find it on the PyPI with a source package and an egg for Python 2.6. The code is also available on github.com.
-
Gitready for your daily knowledge-dosage
Need your daily dosage of "perhaps learning something new"? Why not improve your git-skills at the same time?! On gitready.com Nick Quaranto offers a really nice collections of tips the powerful SCM grouped by skill-level (beginner, intermediate and advanced). Want to contribute a tip? There is also a submit form for you :-)
[via github.com]
-
Git branches and PS1
With the release of Mercurial 1.1 yesterday and me more and more getting into it again I complained on IRC that as much as I love git's named branches, they make it kind of easy to just do something to the wrong branch. If you have a branch per folder it's kind of more obvious in what branch you're operating all the time, in my opinion.
But there is a simple solution for this: Martin today posted a quick guide on how to get the current branch name into your shell's $PS1.
Read more about "Git branches and PS1" ... -
Git and Mercurial branchname in PS1
Primary link: vc.gerg.ca
If you're working with version control systems like Mercurial, Git or SVN (if you must) and there with multiple branches, it's sometimes really hard to keep track of what branch you're currently in. There are a couple of utilities out there that help you integrate that information in your shell's prompt, but most of them are limited to just one versioning system. Gred Ward's vcprompt is different in this regard since it supports Git, Mercurial and some other system I don't want to name here ;-) And it is really fast :D
[via www.mahner.org]
