Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Michael Ang <mang@subcarrier.org>
To: Alan Modra <alan@linuxcare.com.au>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] phase 2 gcc build fails
Date: Thu, 14 Dec 2000 01:27:06 -0500	[thread overview]
Message-ID: <3A38683A.A2FCB51B@subcarrier.org> (raw)
In-Reply-To: Pine.LNX.4.21.0012141355570.2565-100000@front.linuxcare.com.au

Yeah, that's exactly what you wanted to do.  After you ran the "admin
-b" command, the vendor branch was de-vendorised, so I'm guessing that
the next time you pulled you got the trunk, not the branch.  With vendor
branches, you never really know if you're pulling from a branch or the
trunk, hence our desire to avoid them.

	- Mike.

Alan Modra wrote:
> 
> On Thu, 14 Dec 2000, Alan Modra wrote:
> 
> > What I've got to do, I guess, is to commit my tree back to the main truck.
> > eg. in the case of config.if, we want a version 1.2 which will be identcal
> > to version 1.1.1.2
> 
> Seemed to work OK.  A "cvs update -d" in your gcc directory should now
> fix your tree for you.

  reply	other threads:[~2000-12-14  6:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13 23:11 [parisc-linux] phase 2 gcc build fails Matt Taggart
2000-12-14  0:07 ` Alan Modra
2000-12-14  0:20   ` Matt Taggart
2000-12-14  0:31     ` Alan Modra
2000-12-14  2:57       ` Alan Modra
2000-12-14  6:27         ` Michael Ang [this message]
2000-12-14  6:55           ` Alan Modra
2000-12-14 10:20             ` Matthew Wilcox
2000-12-15  5:56               ` Michael Ang
2000-12-15  5:48             ` Michael Ang

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=3A38683A.A2FCB51B@subcarrier.org \
    --to=mang@subcarrier.org \
    --cc=alan@linuxcare.com.au \
    --cc=parisc-linux@thepuffingroup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox