Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: Merging for 2.1.116...
Date: Wed, 19 Aug 1998 23:34:29 +0200	[thread overview]
Message-ID: <19980819233429.57253@alpha.franken.de> (raw)
In-Reply-To: <Pine.LNX.3.96.980818205222.15702E-100000@lager.engsoc.carleton.ca>; from Alex deVries on Tue, Aug 18, 1998 at 08:54:22PM -0400

On Tue, Aug 18, 1998 at 08:54:22PM -0400, Alex deVries wrote:
> Is someone going to take to task merging our latest kernel into 2.1.116?

I exchanged some emails with Ralf, and he said, that he has started merging
with .115. I've commited the newport abscon and g364 fbcon driver, so
he could even test the merged sources:-) But I haven't heard anything since
then from him about the merge.

> It would be really good to get everything in for 2.2.

I doubt, that we will be able to merge all the stuff. But we will see.

> I don't mind taking a stab at it, although I'm supposed to be packing for
> my move to Toronto in two weeks (finally!).

looks like moving time everywhere. I'll move most of my stuff next
weekend.

Thomas.

-- 
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
                   [Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]

  reply	other threads:[~1998-08-19 21:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-19  0:54 Merging for 2.1.116 Alex deVries
1998-08-19 21:34 ` Thomas Bogendoerfer [this message]
1998-08-20  0:28   ` ralf
1998-08-20  6:44     ` Thomas Bogendoerfer
1998-08-21  0:28       ` ralf
1998-08-21 23:22         ` Thomas Bogendoerfer

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=19980819233429.57253@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=adevries@engsoc.carleton.ca \
    --cc=linux@cthulhu.engr.sgi.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