Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Michael Ang <mang@subcarrier.org>
Cc: Matthew Wilcox <matthew@wil.cx>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] 2.4.0 merge mangle our tree?
Date: Thu, 25 Jan 2001 15:06:16 +0000	[thread overview]
Message-ID: <20010125150616.D25242@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.BSF.4.10.10101250940460.22395-100000@cuzea.pair.com>; from mang@subcarrier.org on Thu, Jan 25, 2001 at 09:56:47AM -0500

On Thu, Jan 25, 2001 at 09:56:47AM -0500, Michael Ang wrote:
> On Thu, 25 Jan 2001, Matthew Wilcox wrote:
> > 
> > i'm not sure why i fucked up the branching so badly.  I did:
> > 
> > cvs tag -b LINUS_240_FIXUP
> [What did you do here?  Copy files from a tarball?]

umm.. i did this after i'd merged the 2.4.0 files into my tree.  i didn't
think about doing it on a branch until then.  Should have thought about
it in advance, I guess?

> > cvs ci
> > cvs add (several times, adding new directories and new files)
> > cvs ci
> > cvs -n up
> > cvs rm
> [What kind of files were you removing?]

the ones which `cvs -n up' told me it would have added -- ie the ones
which were deleted by patch.

> You didn't check out or update with the branch tag, so all your changes
> hit the trunk.  I'm not convinced you want to use a branch for merging (I
> prefer doing it on the trunk - it hurts alot but it's over fast) but I
> haven't been following the discussions very closely.

Ugh.  Blah.  The reason I attempted to do it on a branch is that I could
only test it compiled not that it booted (for reasons too complex to
go into here, involving not being able to locate a 110V to 8V AC in
ottawa yet).  Perhaps I should have just not bothered.

> The thing to really avoid is losing local changes.  If you want to do the
> merge on a branch, the best bet is to revert the inadvertent changes to
> the trunk and start over.

Well, I have a directory here which contains what I want to appear in
CVS on the branch.  I'm not getting rid of it!  Would you mind reverting
this mess I've created to before the checkins I did yesterday, and I'll
try again?

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2001-01-25 15:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25  3:46 [parisc-linux] 2.4.0 merge mangle our tree? Grant Grundler
2001-01-25  4:19 ` Michael Ang
2001-01-25 13:02   ` Matthew Wilcox
2001-01-25 14:56     ` Michael Ang
2001-01-25 15:06       ` Matthew Wilcox [this message]
2001-01-25 10:19 ` Richard Hirst
2001-01-25 12:00   ` Richard Hirst
2001-01-25 17:33   ` [parisc-linux] C100 improvements, problems Greg Ingram
2001-01-25 17:36     ` Richard Hirst
2001-01-26 18:16       ` Greg Ingram
2001-02-04 12:11         ` Richard Hirst
2001-01-25 17:42     ` Matthew Wilcox
2001-01-26 18:17       ` [parisc-linux] C100 report, latest CVS bits Greg Ingram
2001-01-25 18:24   ` [parisc-linux] 2.4.0 merge mangle our tree? Grant Grundler
2001-01-25 17:24 ` Matthew Wilcox

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=20010125150616.D25242@parcelfarce.linux.theplanet.co.uk \
    --to=matthew@wil.cx \
    --cc=mang@subcarrier.org \
    --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