On Sat, Oct 7, 2023 at 9:20 AM Christian Couder <christian.couder@xxxxxxxxx> wrote: > > On Sat, Oct 7, 2023 at 1:29 AM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > > > Naomi Ibe <naomi.ibeh69@xxxxxxxxx> 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".
