You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2018/12/30 20:56:53 UTC

[GitHub] Pr0methean removed a comment on issue #79: WIP: [SCM-318] Untag command, with Git implementations

Pr0methean removed a comment on issue #79: WIP: [SCM-318] Untag command, with Git implementations
URL: https://github.com/apache/maven-scm/pull/79#issuecomment-450585089
 
 
   BTW, is it normal for hard-resetting this way to cause push rejections, because Github decides the branch now has unmerged changes from the parent? That's why the last two rounds have included merge commits, although I guess I could've used `git push --force`. It's not the way I'm familiar with using `git reset`, which is to move a branch *back* in time to a previous commit and delete the subsequent history, which of course does require a force push if the deleted commits were pushed. But since your branch was a child of mine, resetting mine to yours shouldn't drop any commits, so I'd think a force push wouldn't be necessary.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services