Hi Mark, Thank you for your help, and I'm sorry I didn't get back to you sooner. > > I have implemented (in script form) a different approach: basically, I just > keep a local copy of the refs pushed out via bundle in refs/remotes/*, just > as for any other remote, and then use those as the basis for later bundles. > My longer term goal is to integrate this into git push, so that with a > properly configured remote "git push foo" will create a bundle based upon > the local knowledge of the remote's basis and update the local copy of the > refs. > > [...] That's a good way to do things. I tend to like my system better because it's a little more flexible and it doesn't pollute git-branch -a and gitk --all, also as I said before I like the bundle creation and the basis update to be separated. How do you deal with the case where you want to include remote refs in the bundle? Don't they get saved as refs/remotes/remote/remotes/somewhere-else/master? Adam -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
