unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tomas Nordin <tomasn@posteo.net>
To: "Mario Krajačić" <krajacic.mario@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: I want to contribute and chose right project for graduate thesis
Date: Fri, 21 Jul 2017 23:16:09 +0200	[thread overview]
Message-ID: <87vaml32zq.fsf@fliptop> (raw)
In-Reply-To: <CACwYE9U90_RwMSZ48PwgiOJygkwow-EtKt5NHo2zv_nNuVnWNw@mail.gmail.com>

Mario Krajačić <krajacic.mario@gmail.com> writes:

> Hello,
>
> I am student of IT from Croatia on finishing year for my bachelor's degree.
>
> For the graduate thesis I would like to contribute some open source
> project. For example it can be  some bug fix. Language in I work is C. My
> knowledge is shown in programs on git profile: https://github.com/mkrajaci

As mentioned elsewhere on this thread, maybe a bug fix is a bit specific
for a thesis work, but doesn't have to be of course. I just wanted to
give a tip on a discussion going on right now on the coreutils list on
the program cut. cut is a program for getting selected delimited fields
from a file. Some people over the years has requested the possibility
for the program to respect the order of the fields specified (cut will
maintain the order of fields in the file). The maintainers thinks this
/might/ be a good feature but will not implement it because it can be
done by combining cut with other tools plus none of them see the
need. They will however re-view patches.

Anyways, see this thread for details:
https://lists.gnu.org/archive/html/coreutils/2017-07/msg00025.html

It is said in that thread that because of how cut is implemented, this
feature addition is non-trivial to implement. If one is prepared for the
possibility that the feature is not added despite it might work to a
certain degree, it could be a very good exercise I imagine. I am sure
they would give help and feedback along the way.



  parent reply	other threads:[~2017-07-21 21:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21  8:46 I want to contribute and chose right project for graduate thesis Mario Krajačić
2017-07-21 16:01 ` Emanuel Berg
2017-07-21 18:40   ` Marcin Borkowski
2017-07-21 20:01     ` Emanuel Berg
2017-07-22  4:10       ` Marcin Borkowski
2017-07-22 16:19         ` Emanuel Berg
2017-07-27 23:15       ` Ken Goldman
2017-07-27 23:27         ` Emanuel Berg
2017-07-28 18:55           ` Marcin Borkowski
2017-07-28 19:50             ` Drew Adams
2017-07-29  2:30               ` Emanuel Berg
2017-08-03 17:39                 ` Marcin Borkowski
2017-07-29  2:22             ` Emanuel Berg
2017-07-21 18:30 ` Kevin Buchs
2017-07-21 19:58   ` Emanuel Berg
2017-07-21 21:16 ` Tomas Nordin [this message]
2017-07-21 22:17   ` Emanuel Berg
2017-07-21 22:22   ` Emanuel Berg
2017-07-22 20:55     ` Tomas Nordin
2017-07-22 21:37       ` Emanuel Berg
2017-07-25 17:39         ` Mario Krajačić
2017-07-25 18:30           ` Emanuel Berg
  -- strict thread matches above, loose matches on Subject: below --
2017-07-22 13:33 Richard Melville
2017-07-22 16:25 ` Emanuel Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vaml32zq.fsf@fliptop \
    --to=tomasn@posteo.net \
    --cc=help-gnu-emacs@gnu.org \
    --cc=krajacic.mario@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).