I've moved the official repo to github: git clone git://github.com/stevedekorte/io.git
Please update your repos and let me know if this works ok.
Cheers,
- Steve
IIRC, it is possible to let git pull from this repo withot branch
specification if you add this script to .git/hooks/post-update on
github
-- snip --
refs="$repodir/info/refs"
git-update-server-info
cat "$refs"
| grep "refs/heads/master"
| sed 'srefs/heads/masterHEAD'
>> "$refs"
-- /snip --
Either way, if the puller switches to the new repo with 'pull' instead of cloning again the whole thing, he/she'll also need to update git
config for default remote repo.
About the sniff: either $repodir or $refs has to be substituted
manually with path to .git or repo directory (if the repo is bare).
These are not git's variables. Probably either .git or . (without
absolute path) works.
Danya -- Can you explain what problem the script solves? I would expect "git clone" to set up my local copy and "git pull" to bring it up to date. This has worked for me with other repos without the code you suggest. Thanks and best regards. -- Ward
IIRC, it is possible to let git pull from this repo withot branch specification if you add this script to .git/hooks/post-update on github -- snip -- refs="$repodir/info/refs" git-update-server-info cat "$refs" | grep "refs/heads/master" | sed 'srefs/heads/masterHEAD' >> "$refs" -- /snip --
Either way, if the puller switches to the new repo with 'pull' instead of cloning again the whole thing, he/she'll also need to update git config for default remote repo.
The script is helpful if you create a repository that other people who
cloned from other repository want to pull from. In this situation the
script allows pullers to avoid explicit branch specification.