From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>, "Yakov Lerner" <iler.ml@gmail.com>
Subject: Re: git todo-list ?
Date: Tue, 24 Apr 2007 12:10:23 +0100 [thread overview]
Message-ID: <200704241210.31378.andyparkins@gmail.com> (raw)
In-Reply-To: <7virbm6ozi.fsf@assigned-by-dhcp.cox.net>
On Tuesday 2007 April 24, Junio C Hamano wrote:
> I miss "kernel traffic" and its cousen "git traffic" (which we
> saw only the first issue of, unfortunately). FWIW, until very
> recently, your "niggles" list $gmane/34244 was still kept in my
> box as 'ticked'. I recently unticked it as many of the issues
> there have been resolved and some have been made irrelevant.
Wow - I feel useful now :-) my current "niggles" list is so small that it's
not worth writing down - is git approaching perfection?
Coincidentally, I was reading through my git-versus-svn post, and found that
similarly an awful lot of the issues for git had gone away. I found it
remarkable that it had happened so fast.
It actually makes it harder for a potential reporter to keep up - git moves
forward so quickly, that if you blink you've missed five new features going
in.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-04-24 11:11 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
2007-04-24 7:22 ` Andy Parkins
2007-04-24 10:33 ` Junio C Hamano
2007-04-24 11:10 ` Andy Parkins [this message]
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=200704241210.31378.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=iler.ml@gmail.com \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.