All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: git@vger.kernel.org, Alex Riesen <raa.lkml@gmail.com>
Subject: Re: Commit f84871 breaks build on OS X
Date: Thu, 07 Dec 2006 14:36:40 -0800	[thread overview]
Message-ID: <7vmz5zqqo7.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <86ejrbihnr.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "07 Dec 2006 12:18:32 -0800")

merlyn@stonehenge.com (Randal L. Schwartz) writes:

>>>>>> "Alex" == Alex Riesen <raa.lkml@gmail.com> writes:
>
> Alex> Strange. You seem to have the old, generated Makefile you perl/
> Alex> directory. Haven't your pull failed? If so, I suspect that
>
> Alex>  rm perl/Makefile
> Alex>  git reset --hard
> Alex>  git pull git...
>
> I ended up having to do another reset afterward.
>
> Definitely something went weird when Makefile was removed
> from .gitignore.

Yes, perl/Makefile is getting overwritten by what Makefile.PL
generates.  I thought the point of Alex's patch was to have it
muck with perl.mak and leave the tracked Makefile alone?


  reply	other threads:[~2006-12-07 22:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 13:54 Commit f84871 breaks build on OS X Brian Gernhardt
2006-12-07 14:33 ` Alex Riesen
2006-12-07 15:20   ` Pazu
2006-12-07 20:18   ` Randal L. Schwartz
2006-12-07 22:36     ` Junio C Hamano [this message]
2006-12-07 22:55       ` Junio C Hamano
2006-12-08  7:40         ` Alex Riesen
2006-12-08 11:51           ` Brian Gernhardt
2006-12-07 14:55 ` Johannes Schindelin
2006-12-07 15:23   ` Andreas Ericsson
2006-12-07 15:29   ` Brian Gernhardt
2006-12-07 15:42     ` Alex Riesen
  -- strict thread matches above, loose matches on Subject: below --
2006-12-07 16:04 Brian Gernhardt

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=7vmz5zqqo7.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.com \
    --cc=raa.lkml@gmail.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 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.