On Apr 15, 2013, at 9:37 PM, Denis Ovsienko 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; the intent, at l
> 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)
>
> W
On Apr 15, 2013, at 7:40 PM, Michael Richardson 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
___
tcpdump-workers mailing
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 peopl
On Apr 15, 2013, at 7:18 AM, François-Xavier Le Bail
wrote:
>> From: Guy Harris
>> If we want to ensure that the configuration scripts we ship are generated by
>> a
>> particular version of autoconf, we should remove configure from the
>> repository,
>> add an autogen.sh script to re-gener
> From: Guy Harris
> If we want to ensure that the configuration scripts we ship are generated by
> a
> particular version of autoconf, we should remove configure from the
> repository,
> add an autogen.sh script to re-generate the configure file, and ensure that
> it's run as part of the rel
