Hi, Linus Torvalds wrote:
> I also don't see why, if OS-X already _does_ include the GNU tools, they
> couldn't be under /opt/fsf/bin or something like that, and then you could
> just do
>
> PATH=/opt/fsf/bin:$PATH
We could prepend /usr/lib/git to $PATH, and symlink them with their "real
On Mon, 11 Jul 2005, Bryan Larsen wrote:
>
> >
> > Most everything includes git-sh-setup-script anyway by now.
> >
> > However, what are the features that break the default apple tools anyway?
> > Maybe we should avoid using them? OSX clearly comes with "cp" and "xargs"
> > regardless, what
Bryan Larsen <[EMAIL PROTECTED]> writes:
> Last night, I couldn't think of alternatives to these, but I obviously
> didn't try very hard. xargs -r can probably happen via a temporary
> file and cp -u can probably be simulated using rsync.
The only user of "xargs -r" in the Linus GIT is git-prune
The only user of "cp -l" in the Linus GIT is git-clone-script
local optimization. I could revert it to the version that I
originally sent to the list, which uses cpio -pld, if your cpio
groks that flag.
Those options are in the man page, at least.
Bryan
-
To unsubscribe from this list: send t
Bryan Larsen <[EMAIL PROTECTED]> writes:
> For the record, "${XARGS} -0r" may be uglier than "xargs -0r", but
> replacing it with several lines of shell magic is a loss.
OK, OK, the one I suggested for xargs was _U_G_L_Y_.
The one Linus suggested looks to me the cleanest. That is, to
give an ex
Junio C Hamano wrote:
Junio C Hamano <[EMAIL PROTECTED]> writes:
The only user of "cp -l" in the Linus GIT is git-clone-script
local optimization. I could revert it to the version that I
originally sent to the list, which uses cpio -pld, if your cpio
groks that flag.
Bryan, does this work
Junio C Hamano <[EMAIL PROTECTED]> writes:
> The only user of "cp -l" in the Linus GIT is git-clone-script
> local optimization. I could revert it to the version that I
> originally sent to the list, which uses cpio -pld, if your cpio
> groks that flag.
Bryan, does this work for you?
--
Linus Torvalds wrote:
On Mon, 11 Jul 2005, Junio C Hamano wrote:
I am not yet convinced "one variable per GNU program" is the
right way to do (I do agree it is a problem and I appreciate
your trying to solving it; an obvious alternative cop-out would
be to fix this in the user's environment, b
Junio C Hamano wrote:
Bryan Larsen <[EMAIL PROTECTED]> writes:
+ for file in $(SCRIPTS); do \
+ sed -e "s/DATE\=date/DATE=$${DATE}/" -e "s/CP\=cp/CP=$${CP}/" -e
"s/XARGS\=xargs/XARGS=$${XARGS}/" -e "s/STAT\=stat/STAT=$${STAT}/" $$file > $$file.new; \
+ cat $$fi
Bryan Larsen <[EMAIL PROTECTED]> writes:
> Update the git Makefile to put the results of config.sh into the scripts.
> config.sh searches for gnu utilities cp, stat, date and xargs.
>
> Signed-off-by: Bryan Larsen <[EMAIL PROTECTED]>
> +install: $(PROG) $(SCRIPTS) config
> $(INSTALL) -m75
On Mon, 11 Jul 2005, Junio C Hamano wrote:
>
> I am not yet convinced "one variable per GNU program" is the
> right way to do (I do agree it is a problem and I appreciate
> your trying to solving it; an obvious alternative cop-out would
> be to fix this in the user's environment, but there might
Update the git Makefile to put the results of config.sh into the scripts.
config.sh searches for gnu utilities cp, stat, date and xargs.
Signed-off-by: Bryan Larsen <[EMAIL PROTECTED]>
---
Makefile | 13 +++--
1 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/Makefile b
12 matches
Mail list logo
