On Wednesday 15 April 2015 04:19 AM, David Bremner wrote: > I'm not sure. Your "fresh install case" seems like about the only one > where moving one without the other makes sense. In any case, maybe > somebody finds the upstream docs at > > http://gitolite.com/gitolite/gitolite.html#moving > > helpful. It isn't exactly right, but should be enough help either > manually or someone constructing a maintainer script.
Actually, I think this bug's severity should be raised. Irrespective of whether it migrated the settings or not, it should still, for newer repositories, create the repo in the new locaiton. Because, by setting up the new path, it gives that impression. Today, I just pushed my kernel repo, and realized that it created the repository at the old location, thus eating my entire rootfs space. I looked at the documentation. I think it is fair in that when a user changes the gitdir location, the migration is on him. That migration is for the *current* (and old) git repositories, including the g3 rc files. But for new and freshly pushed repository, it should honor the new location ? -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: OpenPGP digital signature
