Effective immediately, the main AUR git repo now lives on projects.archlinux.org.
You can find the web interface easily by visiting:
The new pull url is:
http://projects.archlinux.org/git/aur.git
To eliminate confusion, I've unshared my old public repo.
Sorry for the inconvenience, but we'll be staying here a while now!
- P
P.S. Anyone wiser than I in the ways of git, can you share any tricks for telling git that the origin has been relocated? Is it as easy as just changing the origin in the config file or are there more things to do?
P.S. Anyone wiser than I in the ways of git, can you share any tricks for telling git that the origin has been relocated? Is it as easy as just changing the origin in the config file or are there more things to do?
Just changing the url for "remote origin" in the .git/config file should do it. You can do it manually, or using the git-config porcelain.
P.S. Anyone wiser than I in the ways of git, can you share any tricks for telling git that the origin has been relocated? Is it as easy as just changing the origin in the config file or are there more things to do?
It is as easy as changing the origin in the config file. Remote branches are just labels, the config file tells the labels where to check for new patches.
I've a note of warning because I've run into this situation a few times before. When hosting a git repo via http you may have to `git-update-server-info` for people to pull/fetch the recent changes even if gitweb does show the changes.
Loui wrote:
I've a note of warning because I've run into this situation a few times before. When hosting a git repo via http you may have to `git-update-server-info` for people to pull/fetch the recent changes even if gitweb does show the changes.
I didn't know this but Eliott helped me out with this useful tip, so I'm sharing!
If you do:
chmod u+x whatever.git/hooks/post-update
that should run update-server-info after you push changes to it for you... so you don't have to run it manually yourself each time.
- P
Aha!
On 9/26/07, Paul Mattal paul@mattal.com wrote:
If you do:
chmod u+x whatever.git/hooks/post-updatethat should run update-server-info after you push changes to it for you... so you don't have to run it manually yourself each time.
arch-projects@lists.archlinux.org