All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Anderson <ryan@michonline.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC+PATCH 1/1] Move SCM interoperability tools into scm/
Date: Sun, 09 Jul 2006 20:24:34 -0700	[thread overview]
Message-ID: <44B1C872.3050807@michonline.com> (raw)
In-Reply-To: <7vsllae1ik.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 985 bytes --]

Junio C Hamano wrote:
> 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
>   
I think that doing that means I still need to duplicate the  actual
build rules, which is what I was hoping to avoid, as they encode all the
magic "path replacement" logic in multiple places.

On the other hand, I can fix *that*, if I break the ability to run in
the build directory, which is bad in its own way.  (Fixing the tests
should be a matter of adapting the test library slightly, I think.)

For the time being, I'm going with ugly, but less disruptive, and I'm
willing/planning on revisiting it when things shake out a bit more.


-- 

Ryan Anderson
  sometimes Pug Majere



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2006-07-10  3:25 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
2006-07-10  3:24         ` Ryan Anderson [this message]
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=44B1C872.3050807@michonline.com \
    --to=ryan@michonline.com \
    --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 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.