[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Fab-user] Github changes, phase 1: repo move
From: |
Jeff Forcier |
Subject: |
[Fab-user] Github changes, phase 1: repo move |
Date: |
Mon, 4 Jul 2011 20:54:20 -0700 |
Hi all,
I'm about to switch the Github repository bitprophet/fabric (my
personal acct) to fabric/fabric (the Fabric organization).
This is the first step in moving fully to Github: it means that I can
grant commit bits to other folks if needed; and assuming most folks
cloned github/bitprophet/fabric instead of git.fabfile.org/fabric, it
also means this will be the last ever repository move (the org can be
re-admin'd easily.)
If all goes well, this should port over the network itself and the
handful of existing pull requests (most of which should be dupes of
Redmine tickets anyways.)
If you have only set up your own fork as your "origin" remote, no
action is needed. If you had bitprophet/fabric as a remote ("origin"
or otherwise) or were basing off of git.fabfile.org, you'll need to
repoint it:
$ git remote set-url <remote name> https://github.com/fabric/fabric.git
Let the list know if you run into problems pulling from the updated remote.
Thanks,
Jeff
P.S. A quick FYI: I'm giving a short talk on Fabric
(possibly-overlooked existing features + future roadmap) at
Wednesday's San Francisco Django meetup. Pretty sure it's already got
a lot of RSVPs but in case it's not full yet, do drop by. I promise
not to flub my slides too badly :)
http://www.meetup.com/The-San-Francisco-Django-Meetup-Group/events/19789411/
--
Jeff Forcier
Unix sysadmin; Python/Ruby engineer
http://bitprophet.org
- [Fab-user] Github changes, phase 1: repo move,
Jeff Forcier <=