12/13/2023 0 Comments Git tag multiple repositories![]() ![]() One idea is to have one project repo, where you do most of your development, plus several separate repos, from which you distribute modules: proj/.git So you need a more sophisticated solution. But you actually want a combination of single repo and multiple repos, right? You want the benefits of each. The alternative for you is not Subversion, but simply a single repository, which could be in Git, Subversion, or whatever. ![]() That seems fine for awhile, but I've heard nasty war stories. It solves a different problem.) The huge drawback is that you cannot recover an exact contour of your codebase. (Google's Repo tool a wrapper around Git, meant for use with Gerrit, a code-review tool, is sort of similar. That can be useful for coordinated development. There is a big difference though: Most devs, at least during some phase of development, prefer to attach to a branch of each submodule, which is not supported by git-submodules. To commit with svn-submodules, you have to commit in each submodule directory separately, just as with git-submodules. In fact, when you use the -r to attach an svn submodule at a specific revision, the behavior is nearly identical. git-submodules is similar to svn:externals, aka svn-submodules. You could argue that we should have put proj, ext and qa under the same git repository but I thought that would have been against the git philosophy of keeping different concepts in different repositories.ĭoes anyone have a solution (other than writing a script to do git pull on every dir under ~/dev) to this trivial problem? I looked into 'git submodules' and it doesn't provide a single point for 'git pull' to update these three separate modules at the same time. This is not nice someone will always forget to update (git pull) one of these dirs and his project will be out of sync (e.g. With git, we need to do 'git pull' separately for each dir. Under svn, synchronization of these dirs was simple: a single update under ~/dev would update all of them recursively. Proj, ext and qa are different git repositories. Here is what every developers' directory structure looks like: ~/dev/proj For more information, see " Viewing your repository's releases and tags.I am working on a project where we manage external libs/headers and qa with git. You can then view your published or draft releases in the releases feed for your repository. To work on the release later, click Save draft. If you're ready to publicize your release, click Publish release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |