From: Junio C Hamano <gitster@pobox.com>
To: Eric Frederickson <ericfrederickson68@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: A Question from a Hopeful Future Contributor
Date: Fri, 18 Jul 2025 16:15:56 -0700 [thread overview]
Message-ID: <xmqqecud145v.fsf@gitster.g> (raw)
In-Reply-To: <87y0slp23s.fsf@arch.mail-host-address-is-not-set> (Eric Frederickson's message of "Fri, 18 Jul 2025 18:26:31 -0400")
Eric Frederickson <ericfrederickson68@gmail.com> writes:
> Looking through the repo for a place to find todo items, I naturally stumbled
> upon the TODO file in the origin/todo branch,...
Please disregard that file (I should remove it from the repository,
too). It is not curated at all, and the last update to it is more
than 13 years ago.
>> * "git status" on intent-to-add index entries (say "I" in the first
>> column instead of "A" for short status, add "(needs 'git add')" at the
>> end of "new file: $path " in long status).
>
> I am interpreting this todo message as meaning that the following behavior
> should be implemented:
I think that was done long time ago. The entry may have been a wish-item
in April 2011, but not anymore.
Sorry for wasting your time. A better sources of inspiration might
come from list archive searches for the past 3 year or so.
https://lore.kernel.org/git/?q=%22%23leftoverbit%22+d%3A20220718..
But even then, many itches have already been scratched.
As is often said, in open source, the easiest is to start scratching
your own itch ;-)
Thanks.
next prev parent reply other threads:[~2025-07-18 23:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 22:26 A Question from a Hopeful Future Contributor Eric Frederickson
2025-07-18 23:15 ` Junio C Hamano [this message]
2025-07-19 19:57 ` Eric Frederickson
2025-07-26 14:21 ` D. Ben Knoble
2025-07-28 15:02 ` Junio C Hamano
2025-07-28 16:54 ` D. Ben Knoble
2025-07-18 23:31 ` Ayush Chandekar
2025-07-19 22:06 ` Lucas Seiki Oshiro
2025-07-20 1:02 ` Eric Frederickson
2025-07-19 22:16 ` brian m. carlson
2025-07-20 1:22 ` Eric Frederickson
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=xmqqecud145v.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ericfrederickson68@gmail.com \
--cc=git@vger.kernel.org \
/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 NNTP newsgroup(s).