Re: [tcpdump-workers] autoconf 2.61 versus 2.68

2013-04-15 Thread Guy Harris
On Apr 15, 2013, at 7:18 AM, François-Xavier Le Bail fx.leb...@yahoo.com wrote: From: Guy Harris g...@alum.mit.edu 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

[tcpdump-workers] moves to github

2013-04-15 Thread Michael Richardson
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

Re: [tcpdump-workers] moves to github

2013-04-15 Thread Guy Harris
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 ___

Re: [tcpdump-workers] moves to github

2013-04-15 Thread Denis Ovsienko
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

Re: [tcpdump-workers] moves to github

2013-04-15 Thread Guy Harris
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;