From: Junio C Hamano <junkio@cox.net>
To: "Yakov Lerner" <iler.ml@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: git todo-list ?
Date: Mon, 23 Apr 2007 17:54:41 -0700 [thread overview]
Message-ID: <7vslaqbnhq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vlkgid7x4.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Mon, 23 Apr 2007 15:48:07 -0700")
Junio C Hamano <junkio@cox.net> writes:
> "Yakov Lerner" <iler.ml@gmail.com> writes:
>
>> Does git have todo-list ?
>
> We could start one with an entry:
>
> - create a initial set of to-do-list and find a
> volunteer to maintain it.
>
> perhaps at wiki.or.cz/
Arrgh. The url is http://git.or.cz/gitwiki
By the way, I see on that wiki that somebody attempted to have a
list of Wishlist (http://git.or.cz/gitwiki/Wishlist). I think
many of them are now irrelevant, or stale, or have been
rejected. It even includes tongue-in-cheek suggestions made as
counterarguments as if they are serious proposals. I just have
done a minimum clean-up but many of them that I did not touch
are not necessarily there because I agree they are good
suggestions, but because I did not understand what they are
talking about.
As with any "tracking" list, wanting to have one and starting is
the easy part. Unless kept up to date, such a list becomes
quickly useless, or even worse than not having one, leading to
wasted wild goose chase if people look at it without knowing how
stale it is.
And keeping any such list up-to-date takes a lot of effort.
Anybody who attempts it needs to have a lot of time and enough
knowledge to sift through both the list traffic to note not just
the initial issue-raising, but how the issues have been resolved
(or unresolved). I sometimes do that and send out "Unresolved
issues" message to the list myself every once in a while, but as
the maintainer my attention tends to be more on the big-picture
issues and not minor details, and I do not think there are any
unresolved issue at the big-picture level that I haven't talked
about in recent "What's in / What's cooking" messages.
next prev parent reply other threads:[~2007-04-24 0:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 22:44 git todo-list ? Yakov Lerner
2007-04-23 22:48 ` Junio C Hamano
2007-04-24 0:19 ` Jakub Narebski
2007-04-24 0:54 ` Junio C Hamano [this message]
2007-04-24 7:22 ` Andy Parkins
2007-04-24 10:33 ` Junio C Hamano
2007-04-24 11:10 ` Andy Parkins
2007-04-24 14:54 ` Johannes Schindelin
2007-04-24 15:02 ` Johannes Schindelin
2007-04-24 17:21 ` Daniel Barkalow
2007-04-24 18:29 ` Johannes Schindelin
2007-04-24 19:24 ` Andy Parkins
2007-04-24 20:05 ` Junio C Hamano
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=7vslaqbnhq.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=iler.ml@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 NNTP newsgroup(s).