Steven Dake wrote: > > Couldn't corosync-objctl just be changed to use the new APIs? Not super Can and cannot. Can part is, ya, I can keep name and most of the options. Cannot part is, no, for example set operation (create in old objdb) are now strictly typed, so it means different parameters for tool. So I can imagine to keep old name. Most of the parameters are compatible (so -t is still track, nothing is still list, -a is still list_all, ...), but I would really prefer to have name reflecting technology change. > hot on a new bnary but if that is the only way... > > Reviewed-by: Steven Dake <sdake@xxxxxxxxxx> > > > On 12/14/2011 08:41 AM, Jan Friesse wrote: >> corosync-cmapctl is direct replacement for corosync-objctl >> >> Signed-off-by: Jan Friesse <jfriesse@xxxxxxxxxx> >> --- >> tools/.gitignore | 1 + >> ... _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
