On Sun, 20 Mar 2011 16:39:50 -0000, Georg Brandl <g.bra...@gmx.net> wrote: > The reason why rebasing is not universally applied is that the > rebased changesets are different from the original ones (therefore > I wrote A' and B') -- even if the diff is the same, the parents > are not, and therefore the changeset id (hash) changes. This is > called "changing history", and frowned upon by purists. In reality > it works fine if you know the limits: rebasing really only should be > applied if the changesets are not already known somewhere else, > only in the local repo you're working with.
And, as I discovered, only if they are on a single branch. Which is something *none* of the documentation I've read has mentioned. Perhaps that's because named branches are relatively new? -- R. David Murray http://www.bitdance.com _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
