Re: [tcpdump-workers] Work on development
On 05/08/2015 06:53 PM, Jesse Johnson wrote: > I would like to put some effort into the code base. Much appreciated. > What are we using to edit the code and submit changes? Any special rules for > submitting changes? To work on tcpdump/libpcap you don't need any specialized tools. Basic tools like code editor (vim, emacs), C compiler, GNU Make and GNU autotools are pretty much all you need. SCM we use is git. You can find current master branches of tcpdump and libpcap here, https://github.com/the-tcpdump-group Changes are committed to your own fork on GitHub and once you are happy with your patch you can submit Pull Request. If you are new to GitHub here is the link where you can read how does the basic workflow looks like. https://guides.github.com/introduction/flow/ Michal ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] tcpdump-workers Digest, Vol 34, Issue 3
Thanks Michael, Is there a list of things that need to be done ie: bug fixes, new features, documentation, etc...? Jesse On Mon, May 11, 2015 at 12:00 PM, wrote: > Send tcpdump-workers mailing list submissions to > tcpdump-workers@lists.tcpdump.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers > or, via email, send a message with subject or body 'help' to > tcpdump-workers-requ...@lists.tcpdump.org > > You can reach the person managing the list at > tcpdump-workers-ow...@lists.tcpdump.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tcpdump-workers digest..." > > > Today's Topics: > >1. Re: Work on development (Michal Sekletar) > > > -- > > Message: 1 > Date: Mon, 11 May 2015 12:55:12 +0200 > From: Michal Sekletar > To: tcpdump-workers@lists.tcpdump.org > Subject: Re: [tcpdump-workers] Work on development > Message-ID: <55508a90.1000...@redhat.com> > Content-Type: text/plain; charset=windows-1252 > > On 05/08/2015 06:53 PM, Jesse Johnson wrote: > > > I would like to put some effort into the code base. > > Much appreciated. > > > What are we using to edit the code and submit changes? Any special rules > for submitting changes? > > To work on tcpdump/libpcap you don't need any specialized tools. Basic > tools like code editor (vim, emacs), C compiler, GNU Make and GNU > autotools are pretty much all you need. SCM we use is git. You can find > current master branches of tcpdump and libpcap here, > > https://github.com/the-tcpdump-group > > Changes are committed to your own fork on GitHub and once you are happy > with your patch you can submit Pull Request. If you are new to GitHub > here is the link where you can read how does the basic workflow looks like. > > https://guides.github.com/introduction/flow/ > > Michal > > > > > -- > > Subject: Digest Footer > > ___ > tcpdump-workers mailing list > tcpdump-workers@lists.tcpdump.org > https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers > > > -- > > End of tcpdump-workers Digest, Vol 34, Issue 3 > ** > -- Jesse ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] tcpdump-workers Digest, Vol 34, Issue 3
I found the current issues and proposed features on the github page. I will start getting some work done. Jesse On Mon, May 11, 2015 at 12:00 PM, wrote: > Send tcpdump-workers mailing list submissions to > tcpdump-workers@lists.tcpdump.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers > or, via email, send a message with subject or body 'help' to > tcpdump-workers-requ...@lists.tcpdump.org > > You can reach the person managing the list at > tcpdump-workers-ow...@lists.tcpdump.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tcpdump-workers digest..." > > > Today's Topics: > >1. Re: Work on development (Michal Sekletar) > > > -- > > Message: 1 > Date: Mon, 11 May 2015 12:55:12 +0200 > From: Michal Sekletar > To: tcpdump-workers@lists.tcpdump.org > Subject: Re: [tcpdump-workers] Work on development > Message-ID: <55508a90.1000...@redhat.com> > Content-Type: text/plain; charset=windows-1252 > > On 05/08/2015 06:53 PM, Jesse Johnson wrote: > > > I would like to put some effort into the code base. > > Much appreciated. > > > What are we using to edit the code and submit changes? Any special rules > for submitting changes? > > To work on tcpdump/libpcap you don't need any specialized tools. Basic > tools like code editor (vim, emacs), C compiler, GNU Make and GNU > autotools are pretty much all you need. SCM we use is git. You can find > current master branches of tcpdump and libpcap here, > > https://github.com/the-tcpdump-group > > Changes are committed to your own fork on GitHub and once you are happy > with your patch you can submit Pull Request. If you are new to GitHub > here is the link where you can read how does the basic workflow looks like. > > https://guides.github.com/introduction/flow/ > > Michal > > > > > -- > > Subject: Digest Footer > > ___ > tcpdump-workers mailing list > tcpdump-workers@lists.tcpdump.org > https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers > > > -- > > End of tcpdump-workers Digest, Vol 34, Issue 3 > ** > -- Jesse ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] tcpdump-workers Digest, Vol 34, Issue 3
Jesse Johnson wrote: > Is there a list of things that need to be done ie: bug fixes, new > features, documentation, etc...? 1) Reading issues on github is important. 2) the priv seperate work that brooksdavis is doing https://github.com/the-tcpdump-group/tcpdump/pull/455 3) anything with "feature request" https://github.com/the-tcpdump-group/tcpdump/labels/feature%20request ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
