From: Christian Couder <christian.couder@gmail.com>
To: Naomi Ibe <naomi.ibeh69@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [OUTREACHY] Permission To Work On Tasks
Date: Mon, 9 Oct 2023 15:45:13 +0200 [thread overview]
Message-ID: <CAP8UFD2FNGJJahbZtszB-ao1qbr6kYe4ks=u5E5zM-aQYjSkOw@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD0PKAGchx5iqyZqCdua-KYJcrmO2FfNf_vt7xs=+7YL4Q@mail.gmail.com>
On Sat, Oct 7, 2023 at 9:20 AM Christian Couder
<christian.couder@gmail.com> wrote:
>
> On Sat, Oct 7, 2023 at 1:29 AM Junio C Hamano <gitster@pobox.com> wrote:
> >
> > Naomi Ibe <naomi.ibeh69@gmail.com> writes:
> > > Second issue is this https://github.com/gitgitgadget/git/issues/302 .
> > > Is it still available to be worked on? I notice it was opened in 2019
> >
> > Stepping back a bit, do you agree with what the issue says?
> > Remember, these "issue"s are merely one person's opinion and not
> > endorsed by the community.
> >
> > Before you ask "is it still available", do you know the current
> > status (not the status of the "issue")? Have you looked at "git
> > commit --help" to find it out yourself to see if "now" is singled
> > out? Here is what we say in our documentation:
> >
> > In addition to recognizing all date formats above, the --date
> > option will also try to make sense of other, more human-centric
> > date formats, such as relative dates like "yesterday" or "last
> > Friday at noon".
> >
> > So apparently it is still "available". It is a different matter how
> > well a patch that adds "now" to the examples listed there will be
> > accepted, though. During a microproject, one of the things new
> > contributors are expected to learn is to convince others the cause
> > of their patches with the proposed commit log message well.
>
> Yeah, I think this issue, if it is indeed an issue, is not something
> easy to "fix" for a newcomer as it requires to be familiar with our
> documentation and perhaps our code too, or to research them enough to
> understand what a good improvement would be. So you could perhaps do
> it, but it would likely require more work.
Also if it's only a documentation improvement, it might not actually
be a proper microproject as we want them to be "code related".
prev parent reply other threads:[~2023-10-09 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 22:41 [OUTREACHY] Permission To Work On Tasks Naomi Ibe
2023-10-06 23:28 ` Junio C Hamano
2023-10-07 7:20 ` Christian Couder
2023-10-09 13:45 ` Christian Couder [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD2FNGJJahbZtszB-ao1qbr6kYe4ks=u5E5zM-aQYjSkOw@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=naomi.ibeh69@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).