Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Andrew Shugg <andrew@neep.com.au>
Cc: Linux/HPPA List <parisc-linux@parisc-linux.org>
Subject: Re: [parisc-linux] linux-2.4.0
Date: Fri, 2 Feb 2001 02:52:03 +0000	[thread overview]
Message-ID: <20010202025203.C32691@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20010201024930.U4656@neep.com.au>; from andrew@neep.com.au on Thu, Feb 01, 2001 at 02:49:32AM +0800

On Thu, Feb 01, 2001 at 02:49:32AM +0800, Andrew Shugg wrote:
> Alan Cox said:
> > > just for giggles, i merged 2.4.1-pre10 into our tree.  no conflicts.
> > 
> > Bad move. 2.4.1 is incredibly broken and unstable. Stay at 2.4.0 for testing
> 
> Darn.  What did you call the tag before the merge, Mr Wilcx?

Why, LINUS_241_PREMERGE, following our normal convention, of course.

OK, OK, I forgot to lay down the tag.  But I've laid it down retroactively.
I'm about to back the 2.4.1 merge out of the tree, let's see if this works.

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2001-02-02  2:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26  0:48 [parisc-linux] linux-2.4.0 Matthew Wilcox
2001-01-26  1:57 ` Grant Grundler
2001-01-26  3:04   ` Matthew Wilcox
2001-01-31 16:16     ` Alan Cox
2001-01-31 18:49       ` Andrew Shugg
2001-02-02  2:52         ` Matthew Wilcox [this message]
2001-02-13 18:32           ` [parisc-linux] C100 & Latest CVS Bits Greg Ingram
2001-02-13 19:46             ` Grant Grundler
2001-02-13 20:16               ` Greg Ingram
2001-02-13 22:46                 ` Steven Pritchard
2001-02-14 16:17                   ` Auto-rebooting (was Re: [parisc-linux] C100 & Latest CVS Bits) Greg Ingram
2001-01-26 10:23 ` [parisc-linux] linux-2.4.0 Richard Hirst
  -- strict thread matches above, loose matches on Subject: below --
2001-01-25  0:06 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=20010202025203.C32691@parcelfarce.linux.theplanet.co.uk \
    --to=matthew@wil.cx \
    --cc=andrew@neep.com.au \
    --cc=parisc-linux@parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox