On 20.03.14 02:09, Karl P wrote: > > Your patch didn't come inline? I haven't tested this out explicitly, I'm new to email based submission process, so I checked the mailing list, made sure attached patches are accepted, and decided not to take a risk with potentially misconfigured MUA :). I have really no idea how patches get processed on the maintainers' side. Could you please advise any good self-test for submission? I mean, I can send patch to myself first, but how do I make sure it applies cleanly? I use Mozilla Thunderbird.
> but just a note that this would supersede > http://patchwork.openwrt.org/patch/4990/ Yes, but I tried to take into account your changes as well. > Why do you need all the _BASENAME juggling? What is the difference > between "release-v31" and "v31" ? If I understand the author's idea, vN is the start of work on this version, and release-vN is the release. I do have a feeling that I'm reinventing the wheel with _BASENAME, but I couldn't find any other DRY way around. > > Sincerely, > Karl P > > > On 03/19/2014 05:05 PM, Maxim Storchak wrote: >> Hi, >> >> This is an update for luaposix to v31. It provides more interfaces to >> POSIX functions for Lua. There is also a new requirement, luabitop. >> >> Tested on Raspberry Pi in LXC container running OpenWRT. >> >> Signed-off-by: Maxim Storchak <[email protected]> >> >> >> >> _______________________________________________ >> openwrt-devel mailing list >> [email protected] >> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >> > _______________________________________________ > openwrt-devel mailing list > [email protected] > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Best regards, Maxim Storchak mailto:[email protected] _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
