On May 18, 2018, at 11:11 AM, Robin Sommer
> wrote:
What I was envisioning is more or less a clean slate: we'd migrate
over a few tickets, but essentially we'd start with an empty list. I
realize that sounds pretty harsh. However, I hardly ever see any
On Fri, May 18, 2018 at 08:27 -0500, you wrote:
> Doing a half-hearted effort to migrate tickets from JIRA undermines the goal
> of having an authoritative/central location for all code + tickets. Can we
> instead try to deal with it once and for all?
What I was envisioning is more or less a
I am also more in favor of starting clean and manually letting people
move tickets that they think are important over.
But - currently there is a lot in the tracker that are nice to have or
potential problems that I do not ever see getting addressed.
Johanna
On 18 May 2018, at 9:17, Slagell,
On 5/17/18 6:27 PM, Robin Sommer wrote:
> That may be a bit too broad though. How about "still valid and either
> (1) quite important or (2) something we expect will be addresses
> reasonably soon"? We have many old tickets that are technically still
> valid but unlikely to see any work anytime
Hi Johanna,
I should've asked the question differently - If it is possible AND how I
can do it. Sorry! :-)
But after a little bit of looking through the bro source code I found it.
%%{
#include
%%}
Greetings
Dane
Am 18.05.2018 um 20:33 schrieb Johanna Amann:
>>
>> Unfortunatly, to
Hi there,
I want to write a function as a plugin to convert a 4 byte hex string
like "405f612f" to float/double (3.49031 in this case).
An easy way to do so in C++ is this:
#include
union ulf
{
unsigned long ul;
float f;
};
int main()
{
ulf u;
string str ="405f612f";
>
> Unfortunatly, to use "stringstream" I will have to include the
> header file. Is this possible to do in plugin functions?
>
Sure, plugins include libraries/other headers/etc. all the time.
Johanna
___
bro-dev mailing list
bro-dev@bro.org
On 5/18/18 11:11 AM, Robin Sommer wrote:
> What I was envisioning is more or less a clean slate: we'd migrate
> over a few tickets, but essentially we'd start with an empty list. I
> realize that sounds pretty harsh. However, I hardly ever see any
> activity on older tickets in JIRA, and I
On Fri, May 18, 2018 at 9:12 AM Robin Sommer wrote:
>
>
> That said, I'm open to a real porting effort if people do believe it's
> helpful to get all the JIRA tickets into GitHub. What do others think?
>
Having the historical tickets available are useful for searching to see if