Interesting post, but this puzzles me:

On Thursday, March 22, 2012 8:52:12 AM UTC+1, radovan bast wrote:


obviously i wouldn't do this if you have already pushed the commits


I guess it is a problem if some other people commit on the wrong master
branch?

that's right. if commits moved the "wrong" branch and this branch is public
(somebody committed to wrong branch and pushed the commits),
perhaps in the "central" repository, then branch pointers should not be moved
back by rebasing. this is a general recommendation.

if that happened then i would git revert the commits.

there are other ways out but i think they would involve informing other people
where the new master is. i am curious to see whether they are better ways
to solve commits to "wrong" public branches.

best wishes,
  radovan

--
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 git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to