From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Matthias Urlichs <smurf@smurf.noris.de>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] "Recursive Make considered harmful"
Date: Thu, 28 Jul 2005 13:09:37 -0400 [thread overview]
Message-ID: <42E91151.7060004@gmail.com> (raw)
In-Reply-To: <7vk6jac2cv.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
...
> While I agree gitk should not come as part of git package, this
> brings up a different issue.
>
> Ideally, I'd want to see gitk packaged from its repository
> kernel.org:/pub/scm/gitk/git.git/ Paul Mackerras maintains, not
> from GIT one which _will_ lag behind.
>
...
>
> While I _do_ rely on gitk in my git work, and I _do_ like its
> simplicity (just a single file right now), my longer term
> preference is to drop the copy we have in git tree and treat it
> just like the other repository browser, qgit. Our documentation
> should point people at it as part of the Porcelain suite.
Then this should happen sooner rather than later.
next prev parent reply other threads:[~2005-07-28 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 8:39 [PATCH/RFC] "Recursive Make considered harmful" Ryan Anderson
2005-07-27 14:25 ` A Large Angry SCM
2005-07-27 14:37 ` Kirby C. Bohling
2005-07-27 15:32 ` A Large Angry SCM
2005-07-27 21:50 ` Junio C Hamano
2005-07-27 22:07 ` A Large Angry SCM
2005-07-28 7:51 ` Petr Baudis
2005-07-28 9:40 ` Matthias Urlichs
2005-07-28 7:04 ` Junio C Hamano
2005-07-28 7:45 ` Matthias Urlichs
2005-07-28 16:38 ` Junio C Hamano
2005-07-28 17:09 ` A Large Angry SCM [this message]
2005-07-29 6:53 ` Ryan Anderson
2005-07-29 7:31 ` Sam Ravnborg
2005-07-29 7:46 ` Petr Baudis
2005-07-29 9:12 ` Timo Hirvonen
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=42E91151.7060004@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=smurf@smurf.noris.de \
/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.