On Fri, 7 Jun 2013 20:42:07 -0400 Erik Schnetter <[email protected]> wrote:
> I take this to mean that this message does not indicate an important > problem that needs to be addressed. Important, no. Problem, no. Nuisance, yes. SVN has its continuous revision numbers. Git has unique id:s for each commit that don't change, even if they get merged. Bzr has neither. So when a re-write of bzr history happens, one cannot uniquely refer to a commit (AFAIK - except with the verbose commit message). A rewrite of history causes confusion when the new code breaks something that the committer didn't test (chiefly - an other host CPU or target). Then one is in the situation that last week version X passed all tests, today version X doesn't. And then if re-writes of history happen frequently, it quickly becomes a mess. This has happened once or twice. Besides the discussed binding of the repo, I've used 'bzr uncommit' when a push has failed. This is useful when you have one small commit to push. With git I use 'git pull --rebase', which moves all local commits as if appended to the end of what the master is. There is a 'rebase' plugin for bzr too, but I haven't tried it. An other option is to have a separate work tree for pocl from which you merge to a local "clean" pocl tree, and then push that clean tree to lp:pocl. This is especially nice with bigger projects where you can disallow direct pushes to the "master" repository - all commits come via merges. Of course, this is a nuisance in small projects like pocl still is :) kalle ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
