On 05/12/2013 11:54 AM, Sami Kerola wrote: > On 12 May 2013 04:30, Lokesh Walase <[email protected]> wrote: >> I am interested in adding "progress bar" feature to "cp" and "mv" commands. >> For this I downloaded the latest source code GNU-coreutils-8.21. >> >> I have fair knowledge of "C" and can understand the code. >> >> However the code is too big and I m right now confused as to what to do or >> where to start from, or what should I read and which part of code I should >> focus. >> >> Is this too ambitious to start with ? >> >> Kindly guide me. > > Hi Lokesh, > > I am not a maintainer, but I would find it surprising if progress bar > would be accepted this time. > > http://lists.gnu.org/archive/html/bug-coreutils/2007-12/msg00120.html > http://lists.gnu.org/archive/html/coreutils/2010-09/msg00052.html > http://lists.gnu.org/archive/html/coreutils/2011-08/msg00015.html > > But perhaps something could be done with the proposal. Would it make > sense to add 'rejected feature requests' section to > > http://www.pixelbeat.org/patches/coreutils/inbox_apr_2013.html > > and have a link to latest summary in README.hacking? IMHO the rejected > section should contain only features which has already been discussed > couple times, such as the progress bar in cp or mv.
So you're suggesting collating all the "Rejected ideas" sections, from the mailing list summaries to a permanent URL somewhere. That would be useful for both requesters and responders. I've put this in place at: http://www.gnu.org/software/coreutils/rejected_requests.html and linked to it from the appropriate place in README as per this commit. thanks, Pádraig. commit bd001dcd4a2c75f583cce13405bf4ad10b464d4d Author: Pádraig Brady <[email protected]> Date: Sun May 12 13:04:27 2013 +0100 doc: link to the list of rejected feature requests * README: Update the email address best suited to discussing feature requests, and also link to the list of previously discussed and rejected requests. diff --git a/README b/README index a7cbacf..b81897e 100644 --- a/README +++ b/README @@ -207,9 +207,11 @@ Here are instructions for checking out the latest development sources: If your patch adds a new feature, please try to get some sort of consensus that it is a worthwhile change. One way to do that is to send mail to [email protected] including as much description and justification [email protected] including as much description and justification as you can. Based on the feedback that generates, you may be able to -convince us that it's worth adding. +convince us that it's worth adding. Please also consult the list of +previously discussed but ultimately rejected feature requests at: +http://www.gnu.org/software/coreutils/rejected_requests.html
