Denis I tried closing a couple of issues, but ran into a
Denis question. Do existing tags in GitHub issues (v3.5, v3.6,
Denis ... v4.3) mean opened against version N.N or fixed in
Denis version N.N?
let's take this to mean, opened against version N.N.
I have looked through
Should the tickets in SourceForge tracker be closed now?
If there were an automated way to do so - with commenting closed, and a
further comments on the issue at http://github.org/the-tcpdump-group/...; as
the closing comment - that would make sense.
I'm not sure anybody here wants to
Denis == Denis Ovsienko infrastat...@yandex.ru writes:
Denis I tried closing a couple of issues, but ran into a
Denis question. Do existing tags in GitHub issues (v3.5, v3.6,
Denis ... v4.3) mean opened against version N.N or fixed in
Denis version N.N?
let's take this to mean,
1) we have created github.com/the-tcpdump-group. It has copies
of three repositories:
a) libpcap
b) tcpdump
c) tcpdump-htdocs
These are pushed by a nightly cron job from our master machine.
So no, github is not the golden or only copy.
Creating a group means that more
On Apr 15, 2013, at 7:40 PM, Michael Richardson m...@sandelman.ca wrote:
2) Guy Harris has run a source 2 github python script to transfer issues
from SF to github.
If you're curious, it's
https://github.com/ttencate/sf2github
___
2) Guy Harris has run a source 2 github python script to transfer issues
from SF to github. They are at:
https://github.com/the-tcpdump-group/tcpdump/issues
(103 open, 199 closed)
https://github.com/the-tcpdump-group/libpcap/issues
(116, 173 closed)
We need
On Apr 15, 2013, at 9:37 PM, Denis Ovsienko infrastat...@yandex.ru wrote:
I tried closing a couple of issues, but ran into a question. Do existing tags
in GitHub issues (v3.5, v3.6, ... v4.3) mean opened against version N.N or
fixed in version N.N?
Those were copied over from SourceForge;
