From: Junio C Hamano <junkio@cox.net>
To: Andy Whitcroft <apw@shadowen.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] perl bindings fix compilation errors
Date: Mon, 25 Sep 2006 21:54:04 -0700 [thread overview]
Message-ID: <7vfyeftehf.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <4517BEBC.4000002@shadowen.org> (Andy Whitcroft's message of "Mon, 25 Sep 2006 12:34:20 +0100")
Andy Whitcroft <apw@shadowen.org> writes:
> I am somewhat unhappy that a make clean at the top level and remake was
> not sufficient to get a working tree.
Sympathetic I am (since I was bitten by it too), but I am not
sure what the right thing to do.
It is certainly incorrect to say that it is a driver error to
git-pull (or git-checkout to switch branches) without running
"make clean" first to get rid of perl/Git.c while your Makefile
still knows it is a generated file. Our Makefile should be more
helpful.
But the question is Makefile in which branch?
Ideally, if Makefile of each and every branch head currently
alive knew that perl/Git.c is problematic and removed it, then
we would not suffer from this problem. But it's obviously not
practical.
next prev parent reply other threads:[~2006-09-26 4:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 10:03 [PATCH] perl bindings fix compilation errors Andy Whitcroft
2006-09-25 10:25 ` Johannes Schindelin
2006-09-25 11:34 ` Andy Whitcroft
2006-09-25 11:38 ` Johannes Schindelin
2006-09-26 4:54 ` Junio C Hamano [this message]
2006-09-26 8:34 ` Johannes Schindelin
2006-09-27 2:40 ` Junio C Hamano
2006-09-27 9:42 ` Johannes Schindelin
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=7vfyeftehf.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=apw@shadowen.org \
--cc=git@vger.kernel.org \
/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.