git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Wolfgang Denk <wd@denx.de>
Cc: git@vger.kernel.org
Subject: Re: Cannot install git RPM
Date: Tue, 09 Aug 2005 10:13:32 -0700	[thread overview]
Message-ID: <7vr7d3uj7n.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7v3bpjxoi1.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Tue, 09 Aug 2005 05:51:02 -0700")

Junio C Hamano <junkio@cox.net> writes:

>> But the resulting RPM cannot be installed either,  at  least  not  in
>> standard Fedora Core 2/3/4 installations:
>> ...
>> Is there at least some  documentation  which  external  packages  are
>> needed, and where to find these?

The problematic one is git-send-email-script.  

I have to admit that it was a mistake to take that patch; I was
trying to be _too_ inclusive.  The script does not even read
from nor write into a git repository, and the only relevance to
git is that it is useful for people to patchbomb the list with
git generated patches.  In other words, the program may be
useful, but its usefulness does not have much to do with git, so
it does not belong to git.

My short-term plan is to downgrade it to "contrib" status, and
not touch it from the main Makefile.  It will be in the 0.99.4
sources but will not be installed nor made into binary package.
I hope Ryan does not mind this decision.

After we audit the set of tools we currently ship, along with
some other scripts/programs, either we remove it altogether from
our source tree, or create a contrib/ subdirectory and move it
there.

  reply	other threads:[~2005-08-09 17:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09 10:40 Cannot build git RPM Wolfgang Denk
2005-08-09 11:07 ` Cannot install " Wolfgang Denk
2005-08-09 12:51   ` Junio C Hamano
2005-08-09 17:13     ` Junio C Hamano [this message]
2005-08-10  0:30       ` Ryan Anderson
2005-08-10  7:46         ` Wolfgang Denk
2005-08-10 16:23           ` Chris Wright
2005-08-10 16:32             ` Sam Ravnborg
2005-08-10 16:32               ` Chris Wright
2005-08-10 19:44               ` Wolfgang Denk
2005-08-10 20:13                 ` Junio C Hamano
2005-08-10 19:44             ` Wolfgang Denk
2005-08-10 19:57               ` Chris Wright
2005-08-09 13:23   ` Clemens Koller
2005-08-09 15:00     ` Linus Torvalds
2005-08-09 15:36       ` Clemens Koller

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=7vr7d3uj7n.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=wd@denx.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 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).