A few colleagues of mine had the big "aha" experience with git when I showed them gitk --all
That's when they realized the *big* difference ;) Kristian 2012/9/21 Stephen Connolly <[email protected]>: > yes it's showing up with that... I am not a heavy gitk user... intellij has > me spoiled > > On 21 September 2012 13:29, Kristian Rosenvold <[email protected] >> wrote: > >> Remember to always use --all option to gitk :O >> >> Kristian >> >> 2012/9/21 Stephen Connolly <[email protected]>: >> > Actually this might be even better (no assuming a tag) >> > >> > # update poms >> > $ git commit -m "[maven-release-plugin] prepare release surefire-2.12.2" >> > $ git commit --allow-empty -m "[maven-release-plugin] copy tag for >> > surefire-2.12.2" >> > $ git tag surefire-2.12.2 >> > $ git reset --hard HEAD^1 >> > # update poms >> > $ git commit -m "[maven-release-plugin] prepare for next development >> > iteration" >> > >> > but gitk is not showing the tag :-( perhaps you are right kristian... >> some >> > dark git magic going on >> > >> > On 21 September 2012 13:01, Stephen Connolly < >> > [email protected]> wrote: >> > >> >> # update poms >> >> $ git commit -m "[maven-release-plugin] prepare release surefire-2.12.2" >> >> $ git checkout -b temp >> >> $ git commit --allow-empty -m "[maven-release-plugin] copy tag for >> >> surefire-2.12.2" >> >> $ git tag surefire-2.12.2 >> >> $ git checkout master >> >> # update poms >> >> $ git commit -m "[maven-release-plugin] prepare for next development >> >> iteration" >> >> >> >> --------------------------------------------------------------------- >> 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]
