GNU bug report logs - #18802
About the process of development for newbie

Previous Next

Package: grep;

Reported by: Yogi Joshi <y2joshi <at> uwaterloo.ca>

Date: Thu, 23 Oct 2014 02:30:02 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Yogi Joshi <y2joshi <at> uwaterloo.ca>
Subject: bug#18802: closed (Re: bug#18802: About the process of
 development for newbie)
Date: Thu, 23 Oct 2014 04:50:04 +0000

[Message part 1 (text/plain, inline)]
Your bug report

#18802: About the process of development for newbie

which was filed against the grep package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 18802 <at> debbugs.gnu.org.

-- 
18802: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18802
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]
From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Yogi Joshi <y2joshi <at> uwaterloo.ca>, 18802-done <at> debbugs.gnu.org
Subject: Re: bug#18802: About the process of development for newbie
Date: Wed, 22 Oct 2014 21:49:28 -0700

Yogi Joshi wrote:
> Would it be fine to pick some bugs for analysis and work on trivial bug fixes?

Sure, that'd be fine.  You can see the list of bugs here:

http://debbugs.gnu.org/cgi/pkgreport.cgi?package=grep

Your email created a bug report, which I'm taking the liberty of closing.  You 
can reply via email to any of the existing bug reports by sending email to 
BUGNUMBER <at> debbugs.gnu.org.


[Message part 3 (message/rfc822, inline)]
From: Yogi Joshi <y2joshi <at> uwaterloo.ca>
To: bug-grep <at> gnu.org
Subject: About the process of development for newbie
Date: Wed, 22 Oct 2014 20:12:55 -0400

Hi
I am a CS grad. student and a newbie to the list; Sorry for any of the 
trivial questions from my side. I wish to understand the code and 
contribute for fixes / enhancements in the future.
To begin with, how can I approach the details of current open bugs, 
available documentation.
Would it be fine to pick some bugs for analysis and work on trivial bug 
fixes? If so, what's the process for the same.

Thanks,
..Yogi.
This bug report was last modified 10 years and 219 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.