> On Jun 5, 2018, at 4:23 PM, Michael <fax12...@gmail.com> wrote: > > Hey Charles, > > Where and how do you want me to run that query?
In general, after cloning, git commands can be run in the "working copy" directory and deeper. So following the wiki instructions, it's inside the "nut" directory that was created after running "git clone". It will probably say something like this: $ git status On branch master Your branch is up to date with 'github/master'. To test the tripplite_0005 branch, run "git checkout tripplite_0005" and run "make". > > Thanks, > Mike > > On Fri, May 25, 2018 at 5:01 PM, Charles Lepple <clep...@gmail.com > <mailto:clep...@gmail.com>> wrote: > On May 25, 2018, at 5:20 PM, Michael <fax12...@gmail.com > <mailto:fax12...@gmail.com>> wrote: > > > > driver.version: 2.7.4-480-g14301bdb > > > > I might not have provided enough information on the branch. 14301bdb > corresponds to a commit on the master branch, rather than the tripplite_0005 > branch that has the new code. What does "git status" say? > > The hex debug output is probably still useful, but I haven't looked at all of > the files. >
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser