From: Junio C Hamano <junkio@cox.net>
To: Ryan Anderson <ryan@michonline.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC+PATCH 1/1] Move SCM interoperability tools into scm/
Date: Sun, 09 Jul 2006 17:39:47 -0700 [thread overview]
Message-ID: <7vsllae1ik.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060709222308.GA4153@h4x0r5.com> (Ryan Anderson's message of "Sun, 9 Jul 2006 15:23:09 -0700")
Ryan Anderson <ryan@michonline.com> writes:
> Comments on a way to make the Makefile less repetitive would be
> appreciated, though.
One obvious way would be not to have scm/Makefile but have the
dependencies in the main Makefile to say (the moral equivalent
of):
git-archimport.perl: scm/git-archimport.perl
next prev parent reply other threads:[~2006-07-10 0:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 6:17 [RFC+PATCH 1/1] Move SCM interoperability tools into scm/ Ryan Anderson
2006-07-09 14:31 ` Johannes Schindelin
2006-07-09 21:26 ` Martin Langhoff
2006-07-09 22:13 ` Petr Baudis
2006-07-09 22:21 ` Johannes Schindelin
2006-07-09 22:23 ` Ryan Anderson
2006-07-10 0:39 ` Junio C Hamano [this message]
2006-07-10 3:24 ` Ryan Anderson
2006-07-09 22:34 ` Timo Hirvonen
2006-07-10 0:20 ` Ryan Anderson
2006-07-10 9:45 ` 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=7vsllae1ik.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=ryan@michonline.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).