I can cut the release, we just need to decide when and what goes in it. I have one change I need to get submitted yet, probably get to it next week sometime.
On 3/6/2014 6:28 AM, Petter Reinholdtsen wrote: > [Thomas Renninger] >> Hi, >> >> not sure what the plans are for another version update. > I do not know either. I guess it depend on someone doing the work to > wrap up a release. Any volunteers? :) > >> Because of git commit: >> >> -------------------- >> commit c18ec02f3304ce2a889a50e378f07a4168af3884 >> Author: Petter Reinholdtsen <p...@hungry.com> >> Date: Wed Feb 5 17:30:32 2014 +0100 >> >> Move all files one level up in the file hierarcy, to avoid the useless >> ipmitool directory. >> -------------------- >> >> An ipmitool-1.8.13.tar.bz2 tarball including plain version 1.8.13 >> will never patch with new mainline commits. >> >> Typically packagers use latest version tarballs and cherry pick >> additional critical patches on top. >> Or add a "patch to latest git head" on top: >> git diff IPMITOOL_1_8_13 HEAD >> >> This does not work now anymore or would need adjusting of every >> single patch. >> >> A new version release/tag would solve this issue. > I do not understand what you mean here. What is it that 'patch -p1' > can't solve? > > > -- > --- Jim Mankovich | jm...@hp.com (US Mountain Time) --- ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
