Re: [Lua-users-stdlib] Getting v34 released

[Reuben T. <rr...@sc...>]

On 25 March 2013 08:12, Gary V. Vaughan <ga...@va...> wrote:

> Hi Reuben,
>
> On 25 Mar 2013, at 08:48, Reuben Thomas <rr...@sc...> wrote:
> > On 25 March 2013 01:44, Gary V. Vaughan <ga...@gn...> wrote:
> > > That would be nice, provided my recent patch to getopt goes in. In
> fact, preferably everything up to 47d51c718ce. Is that possible without
> messing with history?
> >
> > No it's not.  And github (rightly) don't allow rewinding on master, so I
> just committed a revert for the premature branch merge.  master builds and
> meets specs using both Lua 5.1 and 5.2 for me.  Feel free to release, or
> ping me if you like me to do it.
> >
> >
> > I'm unclear why you couldn't just tag before the bit you reverted? But
> fine, making a release now is good.
>
> So that the commits you made to master after the premature merge
> (particularly changes to the release rule) are available while making the
> release.
>

Ah, the reason I was puzzled is that the changes I mentioned I need in the
release were all before the mistaken branch merge.