Technically I don't think you are, as you're pushing the 2.12.2 commit directly to a remote tag, rewriting LOCAL history, and pushing that to master.
At what point in this set of commands is the maven artefact pushed to the remote repository? It would seem that poms mentioning 2.12.2 would never been seen in the master branch's history? So without looking for other tags, there might be no evidence of a release ever actually happening? Maybe I'm missing something tho :) On 22/09/2012, at 5:30 PM, Kristian Rosenvold <[email protected]> wrote: > I'm not rewriting published history. Check the commands again if you > think I am :) > > Kristian > > Den 22. sep. 2012 kl. 01:55 skrev Mark Derricutt <[email protected]>: > >> Please NO. Just stop there. Please - for the sake of sanity. >> >> If you've a pushed a commit off site, its generally considered bad form to >> alter history. Even if its instantaneous and no one will be none the wiser. >> It just feels like a bad practise. >> >> On 22/09/2012, at 12:15 AM, Kristian Rosenvold >> <[email protected]> wrote: >> >>> tocuh poms to 2.12.2 >>> git commit -m "[maven-release-plugin] copy tag for surefire-2.12.2" >>> git push origin HEAD:refs/tags/surefire-2.12.2 >>> touch poms to 2.13-SNAPSHOT >>> git commit --amend -m"[maven-release-plugin] prepare for next development" >>> git push origin HEAD:master >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
