Historic archive of defunct list cerowrt-commits@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: noreply@github.com
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] 21b08e: Gnuplot for lua
Date: Thu, 5 Jan 2012 09:10:44 -0800	[thread overview]
Message-ID: <20120105171044.9080C42682@smtp1.rs.github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/dtaht/deBloat

  Commit: 21b08eb70196bcff0d21bae0985f00d103fb2444
      https://github.com/dtaht/deBloat/commit/21b08eb70196bcff0d21bae0985f00d103fb2444
  Author: Dave Taht <d@taht.net>
  Date:   2012-01-05 (Thu, 05 Jan 2012)

  Changed paths:
    A test/gnuplot_t.lua

  Log Message:
  -----------
  Gnuplot for lua


  Commit: 2ce3f7b6fbf9ee0a977871b105db177576c734af
      https://github.com/dtaht/deBloat/commit/2ce3f7b6fbf9ee0a977871b105db177576c734af
  Author: Dave Taht <d@taht.net>
  Date:   2012-01-05 (Thu, 05 Jan 2012)

  Changed paths:
    A lua/orgtable.lua

  Log Message:
  -----------
  Adding my collection of lua routines from random places

One problem with adopting a less widely known language is
to assemble a useful toolkit.


  Commit: 393d51968a4d85be0182fdfcf400c05fa26260f8
      https://github.com/dtaht/deBloat/commit/393d51968a4d85be0182fdfcf400c05fa26260f8
  Author: Dave Taht <d@taht.net>
  Date:   2012-01-05 (Thu, 05 Jan 2012)

  Changed paths:
    A test/gnuplot_examples/ab.gnu
  A test/gnuplot_examples/multiplot.gnu
  A test/gnuplot_examples/ping2.gnu
  A test/gnuplot_examples/pingplot.gnu
  A test/gnuplot_examples/random.gnu
  A test/gnuplot_examples/testtikz.gnu

  Log Message:
  -----------
  Am carrying around a bunch of gnuplot examples for reference

Gnuplot is no fun.


  Commit: cc7432f811d790a059d390cb7b10a341b6c7c385
      https://github.com/dtaht/deBloat/commit/cc7432f811d790a059d390cb7b10a341b6c7c385
  Author: Dave Taht <d@taht.net>
  Date:   2012-01-05 (Thu, 05 Jan 2012)

  Changed paths:
    A lua/db.lua
  A lua/fromcsv.lua
  A lua/gnuplot_t.lua
  A lua/lisplike.lua
  R src/fromcsv.lua
  R src/lisplike.lua
  M src/staqfq.lua
  R test/ab.gnu
  R test/beatup
  R test/bench
  R test/bigbeatup
  A test/bin/beatup
  A test/bin/bench
  A test/bin/bigbeatup
  A test/bin/lab
  A test/bin/lab2
  R test/db.lua
  M test/ftest.lua
  R test/gnuplot.org
  R test/gnuplot_t.lua
  R test/iperf.csv
  R test/itest
  R test/itest2
  R test/itest4
  R test/itestc
  R test/lab
  R test/lab2
  R test/multiplot.gnu
  R test/ping2.gnu
  R test/pingplot.gnu
  R test/random.gnu
  R test/testtikz.gnu

  Log Message:
  -----------
  Reorg of subdirs,etc.

I need to come up with a cleaner way of doing these tests,
formally design each module, and automate.

Moved all the bql-14 related data into one place, where
it can get sorted through later. As the data was only
valid for 2 days before the code it was testing changed,
I may not bother, however, as an example of the different
sorts of tests and comparisons needed to be run, it should
be a useful thing to automate from.


Compare: https://github.com/dtaht/deBloat/compare/ffc37f6...cc7432f

                 reply	other threads:[~2012-01-05 17:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120105171044.9080C42682@smtp1.rs.github.com \
    --to=noreply@github.com \
    --cc=cerowrt-commits@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox