unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: raphael.berbain@free.fr (Raphaël Berbain)
Subject: Re: Building on OS X
Date: Fri, 27 Dec 2002 16:27:09 +0100	[thread overview]
Message-ID: <85ptrn8otu.fsf@ID-110038.user.dfncis.de> (raw)
In-Reply-To: tsl1-7FA5DE.10001127122002@newsstand.cit.cornell.edu


Timothy Larkin wrote:

> The problem has turned out to be the presence in 3 files of the lines
>
> <<<<<<< darwin.h
> =======
> >>>>>>> 1.10
>
> either in sequence or in close proximity.  Any idea why these lines 
> should appear?  They appear, for instance, in <darwin.h>, and I know 
> they are not legal C code.

They should not appear - at least, they should never stay for a long
time.

I know nothing about OS X, Darwin, or the Emacs source code base.
However, this strongly looks like a cvs unresolved conflict.  The text
that appears between '<<<<<<< darwin.h' and '=======' is the version
that was in a local darwin.h file, while the text between '======='
and '>>>>>>> 1.10' is the version that was in the cvs repository when
the conflict occured.

So either you modified your local copy of darwin.h in a way that cvs
was unable to merge with the repository version, in which case you
should resolve the conflict locally (which often means choosing the
right portion, but can be much trickier - if you are in this case
though, chances are big that you are quite familiar with this portion
of the code), or somebody else made that conflict appear, and checked
it in the cvs repository by mistake - and then it appeared in your
local version when you cvs update'd.  In this case, cvs log and
history commands can help you find who did it so it can be resolved
with its help - look for changes between revisions 1.10 and 1.11.

-- 
Raphaël

  reply	other threads:[~2002-12-27 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-26 15:03 Building on OS X Timothy Larkin
2002-12-26 15:52 ` Kai Großjohann
2002-12-26 16:58   ` Hugo Wolf
2002-12-27 15:00 ` Timothy Larkin
2002-12-27 15:27   ` Raphaël Berbain [this message]
2002-12-27 15:41   ` Rodney Sparapani
2002-12-27 20:22   ` Kai Großjohann

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85ptrn8otu.fsf@ID-110038.user.dfncis.de \
    --to=raphael.berbain@free.fr \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).