On Sun, Apr 6, 2008 at 5:56 PM, Jeff King <peff@xxxxxxxx> wrote: > On Sun, Apr 06, 2008 at 05:22:39PM +0100, seventh guardian wrote: > > > I can, but it is a local commit. It seems like local commits aren't > > being "cloned over" to the slaves.. As I said, this only happens for > > "local masters" where I have local commits. If my master is untouched, > > then I can successfuly clone the repo. > > You are going to have to clarify what you mean by "local commit" and > "local master". Those aren't terms that are commonly used, so I don't > understand what you are talking about. Can you describe which git > commands you used to create this situation? I figured ;) Let me see if I can explain it better: remote master: the project git server, located remotely over the internet local master: my laptop repository, made by cloning the project master repo slave(s): my local machines, which clone the local master, instead of the remote master (to save bandwidth) So on the local master (my laptop) I did: $ git-clone http://remote.master.address/foo/bar.git Because I had to do some local changes to the code (what I've called a "local commit"), I did this on the local master: $ git-commit -a Now I want a copy of the repository on another machine, "slave". So I do this: $ git-clone ssh://local.master.address/path/to/repo Which gives the annoying error.. If I skipped the "local commit" stuff, then the cloning would work perfectly. I hope this is clear now.. Thanks! Renato -- 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
