and of course by f5b9d04a6905b7ad7f45c89e0872436ab6f55b3b
I actually meant f8442e1ab4a5c609f17d075a7a4c55e63251f75b On 04/12/2012 03:33 PM, Olivier Bilodeau wrote: > Ok, I messed up, and I pushed out an earlier version tagged as > packetfence-3.3.0. I then fixed something, and retagged the *fixed* tree > as packetfence-3.3.0 again. > > If you got the wrong tag, and want the new one, please delete > the old one and fetch the new one by doing: > > git tag -d packetfence-3.3.0 > git fetch origin tag packetfence-3.3.0 > > to get my updated tag. > > You can test which tag you have by doing > > git rev-parse packetfence-3.3.0 > > which should return f5b9d04a6905b7ad7f45c89e0872436ab6f55b3b if you have > the new version. > > Sorry for the inconvenience. > > p.s.: this was pasted from `git help tag` see -- Olivier Bilodeau obilod...@inverse.ca :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Packetfence-devel mailing list Packetfence-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-devel
