From: Linus Torvalds <torvalds@osdl.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: What will happen to git.git in the near future
Date: Sun, 1 Oct 2006 13:23:16 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610011318100.3952@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0610012208410.14200@wbgn013.biozentrum.uni-wuerzburg.de>
On Sun, 1 Oct 2006, Johannes Schindelin wrote:
>
> The problem is that the Makefile does not realize that Git.xs no longer is
> there. Neither does the code which recreates the Makefile.
No. The problem is that top-level dependency rules for perl/Makefile are
simply _wrong_. It claims it depends on some things (which is true), but
then it totally ignores _other_ things that it also depends on.
Further, even if it was right, the rules to actually _generate_ the
Makefile then seems wrong, in that it cares about files it shouldn't care
about in the first place.
So why do that at all? Why accept such crap?
Linus
prev parent reply other threads:[~2006-10-01 20:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 10:37 What will happen to git.git in the near future Junio C Hamano
2006-09-24 11:04 ` Petr Baudis
2006-09-24 16:56 ` Rene Scharfe
2006-09-24 18:33 ` Johannes Schindelin
2006-09-24 18:42 ` A Large Angry SCM
2006-10-01 10:16 ` Junio C Hamano
2006-10-01 18:38 ` Linus Torvalds
2006-10-01 18:47 ` Junio C Hamano
2006-10-01 19:56 ` Linus Torvalds
2006-10-01 18:53 ` Johannes Schindelin
2006-10-01 19:57 ` Linus Torvalds
2006-10-01 20:11 ` Johannes Schindelin
2006-10-01 20:23 ` Linus Torvalds [this message]
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=Pine.LNX.4.64.0610011318100.3952@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--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 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).