On Fri, Feb 27, 2009 at 10:11:59PM +1100, Ben Finney wrote: > > > * With many repos you have to somehow keep track of them all so you > > need a tool like mr, one more tool to learn, and that means you need > > to manage a mrconfig file. > > I don't know what “keep track of them all” would mean beyond simply > navigating the filesystem.
If you've been working feverishly, maybe you've had to much coffee, it comes to the end of the day and you have to commit what you've changed. With one git repo a simple git status will show you what you need to do. With many repos, you would have to do git status many times, probably you'd forget to commit some changes. Same with committing, pushing and pulling and checking out new repos. mr lets you do these commands on multiple repos at once but it adds the trouble of managing mr and its mrconfig file. > > * With one big repo git log gives you a global history of all your > > files, a sort of log of what you've been doing on a day-to-day > > basis. This can be really handy. For example I have to meet with my > > supervisors every few weeks. Instead of using my memory I can just > > use git log to help me construct a progress report. > > It also sounds like an awful mess. I want the log to show what I've > been doing in the context of the specific working tree, without the > dozens of other things going on in the same home directory. You can easily do that with one repo though. If I want a log of what I changed in the my_new_project dir in my big git repo, then I do `git log my_new_project`. But if I want a log of everything I do just `git log`. _______________________________________________ vcs-home mailing list firstname.lastname@example.org http://lists.madduck.net/listinfo/vcs-home