From: "Jarkko Hietaniemi" <jhi@xxxxxx>
Thanks (also to Jacob Keller), the git-notes might work in some cases.
But it's obviously a pasted-on solution, requiring a different usage,
e.g. "git log --notes", and whatever other UIs do with it.
One more thing, if you know that no one has fetched the branch you
just
pushed yet, you can amend the commit and force-push it without any
problems (I'd sugget using --force-with-lease).
In my particular case, not going to work, multiple CI engines jump
hungry at every commit.
Sound like you need an intermediate repo (similar in style to a personal
github repo) between your personal machine and the CIs so that you get
the chance to do those rebases/amendments, before you finally push to
the CI.
It's almost the same human psychology issue as realizing what to do
_after_ sending an email asking for help (and wanting to recall the
email...).
To me, part of the sucess of a DVCS is having that extra layer where
control has been distributed to you, rather than control still being
with 'them'.
</bikeshedding>
--
Philip
--
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