Historic archive of defunct list bismark-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bismark-devel@lists.bufferbloat.net
Subject: [Bismark-devel] No new files in bismark-packages??
Date: Tue, 17 May 2011 20:32:44 -0600	[thread overview]
Message-ID: <BANLkTik5tQDB=dMGMkjVowkeK92WjB6J3w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]

There have been no updated files put in bismark-packages since sunday.

I was under the impression that there was a new configuration file added,
and a new version
of walters stuff checked in. Where is are they *exactly*? Are they supposed
to be pulled in from somewhere I am not aware?

I am firing off a new build regardless. After I do this build I will attempt
a clean build.

The build is taking place on huchra in the ~bismark/src/capetown-wndr3700v2
subdirectory.
The package database is in the ~bismark/src/bismark-packages.

These are the last commits I see:

commit 41347492eb7db28f0f0fc0d53a3c810d7a085c44
Author: Bismark Build <bismark@lists.bufferbloat.net>
Date:   Sun May 15 13:15:41 2011 -0700

    Added hosts.list and world_ips.list to /etc/bismark/

commit 6636687c7febf6eb06216b3582bbf934cf8eac80
Author: Bismark Build <bismark@lists.bufferbloat.net>
Date:   Sat May 14 16:47:34 2011 -0700

    Added bismark-mstats

commit 9750b84d5490fb2be5d71b7696181b8616954386
Author: Bismark Build <bismark@lists.bufferbloat.net>
Date:   Fri May 13 07:45:26 2011 -0700

    fixed recovery shell bug
    added multi-port prober


-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com

[-- Attachment #2: Type: text/html, Size: 1590 bytes --]

             reply	other threads:[~2011-05-18  2:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18  2:32 Dave Taht [this message]
2011-05-18  2:49 ` Srikanth Sundaresan
2011-05-18  2:54   ` Poole, Brian
2011-05-18  3:10     ` Dave Taht
2011-05-18  7:15       ` Walter de Donato

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='BANLkTik5tQDB=dMGMkjVowkeK92WjB6J3w@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bismark-devel@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