-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
name of _this_ repository? #6
Comments
Care to share the links ? I'm hitting rock as first links if I do that. One unfortunate naming is that we originally named 'autoproj' the orocos-toolchain buildconf repository. Given that a lot of people depend on that, I never took the pain of renaming it. In any case, this repository is very recent, I am really not surprised that google does not give it first. |
its the third link... I understand that it causes a fixed amount of pain to rename it. Keeping it like it is causes an unbounded amount of confusion over time... ;-) |
That's a very interesting way of putting it. What could save us is that -- I believe -- github actually redirects URLs of renamed repositories. |
👍 for renaming this package. github tracks the name, the old name keeps valid until someome create a name with the package. I don't know where this name is used but i assume we can update it therefore 👍 for rename this now |
You will have to make sure the orocos-toolchain scripts / people are aware of the change. |
When I search google for autoproj git to find a place for sending patches the third hit takes me here... into a repository which is called package_set elsewhere. Even worse, the actual autoproj-repository is called autoproj there...
The text was updated successfully, but these errors were encountered: