On Wed, 10 Oct 2012 08:10:51 -0700 (PDT)
maxhodges <m...@whiterabbitpress.com> wrote:
> I have a git repo with multiple "origin" branches.
Do I understand right that you have a configured remote named "origin"
(either by creating that repo via cloning, which created such a remote
automatically or by running something like `git remote add origin URL`),
and you do fetch from that remote so Git created the so-called "remote
branches" to track state of that remote repository for you?
If this is indeed the case, such branches are named "remote branches".
Yes, the name is confusing, but better stick to this universally
agreed-upon naming convension so everyone things about the same things.
> WHen I add a new branch and commit changes, it shows that each of
> these branches are identical, so it may be writing the commits to
> multiple branches.
Impoissible unless you commit using a tool which does something wicked.
Committing in plain Git only updates the HEAD reference and also an
appropriate branch reference, if HEAD points to a branch. So it's
impossible to update several branches at one when doing a commit --
only the currently checked out branch is updated (the most usual case)
or no branch at all (but ignore this for now).
Well, it's also possible to do anything by writing a post-commit hook,
but I also doubt this is your case.
Another possibility is that what you tell us here is not what you
actually do. Note that Git does *not* touch remote branches unless it's
performing `git fetch origin` which is specifically meant to download
all the history from origin, not present in the local repo, and update
the remote branches accordingly.
> I think made I made some rebase mistake.
I cannot imagine a way in which rebasing might break something in a way
you describe. Note that
> Is there anyway to sort this out, it doesn't work like it used to and
> its confusing. Or should I just delete the repo and start tracking
> with a new repo?
Start from pasting here the contents of your .git/config followed by
the output of `git branch -a`.
Next, paste the first handful of relevant lines of output generated
by running `git log --all --oneline --graph --decorate`
then commit to a branch (be sure to tell us which branch you committed
to) and then paste the output of that `git log ... --graph ...` once
again so we could naturally see what happened.
Otherwise we're condemned to do plain guessing.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at