On Tue, Jul 17, 2012 at 2:01 AM, Ildar Mulyukov <[email protected]> wrote: > On 17.07.2012 10:47:23, Hisham wrote: >> On Tue, Jul 17, 2012 at 12:14 AM, Ildar Mulyukov >> <[email protected]> wrote: >> > On 12.07.2012 11:30:38, Hisham wrote: >> >> Hello, >> >> >> >> I'm happy to announce LuaRocks 2.0.10. >> > [...] >> >> http://luarocks.org/releases/luarocks-2.0.10.tar.gz >> > >> > Again can't see it in GIT :( >> >> Oops, it's now pushed. In any case, the release tarball is the >> authoritative source for versions. > > As I see, you don't use GIT as the base SCM for your development :( .
The truth is that I use it, but I'm terrible at git. I've been a CVS and Subversion user for years and I only know the basics of Git, and often I get things wrong, such as... > E.g. v2.0.10 tag is *ahead* of the master branch. How did *that* end up happening? Here's what I did, based on my shell history: git commit -a # to commit the last-minute 2.0.10 stuff git tag v2.0.10 git push --tags Now, just to check, I did git pull git push and it reported: ]git pull Already up-to-date. ]git push Total 0 (delta 0), reused 0 (delta 0) To [email protected]:keplerproject/luarocks.git 44de5cc..64153c9 master -> master And even though "pull" said "already up-to-date" and "push" said "0, 0, 0, 0", which made me think nothing really happened... *now* master seems to match v2.0.10 in Github... I think? Oh well. -- Hisham http://hisham.hm/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
