On Tue, Feb 21, 2017 at 11:24 AM, Animesh Kashyap
wrote:
> On Sun, Feb 19, 2017 at 12:20 AM, Eugene Syromyatnikov
> wrote:
>> Well, strace itself does not utilise bug tracker of any sort; bugs and
>> suggestions usually reported via this mailing list
On Sun, Feb 19, 2017 at 12:20 AM, Eugene Syromyatnikov wrote:
> Well, strace itself does not utilise bug tracker of any sort; bugs and
> suggestions usually reported via this mailing list (like suggestion
> [1], reported recently). You can try to have a look at lists of bugs
>
On Sat, Feb 18, 2017 at 6:24 PM, Animesh Kashyap wrote:
>
> Are there any flags indicating "easy-to-fix" bugs or "minor" bugs that
> I can get started with. That would be really helpful.
Well, strace itself does not utilise bug tracker of any sort; bugs and
suggestions
On Sat, Feb 18, 2017 at 10:59 PM Eugene Syromyatnikov wrote:
>
> Hello.
>
> Please take a look at the following:
> * https://sourceforge.net/p/strace/wiki/GoogleSummerOfCode2017/
> contains information regarding strace in regards to GSoC 2017
> *
Hello everyone,
I am Animesh Kashyap and I am a 2nd year undergraduate student taking
Computer Science and Engineering course at my university. I want to
participate in Google Summer of Code this year and I like programming
very much but do not have much experience with system programing as
such.
Hello everyone,
I am Animesh Kashyap and I am a 2nd year undergraduate student taking
Computer Science and Engineering course at my university. I want to
participate in Google Summer of Code this year and I like programming very
much but do not have much experience with system programing as such.
Hi
I’m I’m looking forward to contributing to strace development. I’m familiar
with systems programming, syscalls, and OS, esp. linux so I was wondering where
would I begin if I were to start by familiarising my self with the codebase,
fixing a few bugs, etc. My GitHub is at