Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Grant Grundler <grundler@cup.hp.com>
Cc: Matthew Wilcox <matthew@wil.cx>, parisc-linux@puffin.external.hp.com
Subject: Re: [parisc-linux] CVS linux Vs. -test10
Date: Tue, 21 Nov 2000 11:34:32 +0000	[thread overview]
Message-ID: <20001121113432.B883@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200011201734.JAA18526@milano.cup.hp.com>; from grundler@cup.hp.com on Mon, Nov 20, 2000 at 09:34:31AM -0800

On Mon, Nov 20, 2000 at 09:34:31AM -0800, Grant Grundler wrote:
> Ok. What's the first step to getting arch/parisc* and include/asm-parisc*
> into Linus's tree?

Someone (probably me) sends him a patch.  He told me at the Toronto
show that he was quite happy to apply anything that only touched those
two directories. (oh, and drivers/gsc wouldn't be a problem either).
Can I just check that no-one wants to rename drivers/gsc again?  :-)

> I had dinner with Bdale Garbee last night and one of two things he made
> clear was we need to unfork from debian and linus's tree in order to move
> forward. All our CVS branches need to become obsolete or "local sandboxes"
> of the respective upstream partners. Feeding kernel bits upstream will
> bring a new level of visibility (and *HELP*) to the parisc-linux port.

that's true.  last time we discussed this several people were unhappy
with the idea of sending our current work to Linus.  Is anyone unhappy
with doing this now?

> I also find it odd that glibc is merged upstream *before* the kernel is.

glibc is more portable :-)

> The part you described above is the easy part - np.
> I'm worried about labels and tracking how we "name" the releases.
> Mang or other CVS ninja's care to comment?

don't tag it.  just commit it.  tags are laid down at big events, not
when you fix bugs or undo changes.

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2000-11-21 11:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-14 16:35 [parisc-linux] CVS linux Vs. -test10 Paul Bame
2000-11-18  7:24 ` Matthew Wilcox
2000-11-20  7:44   ` Grant Grundler
2000-11-20 11:17     ` Matthew Wilcox
2000-11-20 17:34       ` Grant Grundler
2000-11-21 11:34         ` Matthew Wilcox [this message]
2000-11-21 21:24           ` Grant Grundler
2000-11-22  0:53             ` Matthew Wilcox
2000-11-22  6:54             ` Ryan Bradetich
2000-11-22  7:18               ` Grant Grundler
2000-11-22 20:11             ` Grant Grundler
2000-11-30  8:09         ` Stephen Zander
2000-11-30 15:44           ` Randolph Chung
2000-11-30 16:16           ` Alan Cox
2000-11-30 16:18           ` Paul Bame
2000-11-20 19:23   ` Grant Grundler
  -- strict thread matches above, loose matches on Subject: below --
2000-11-22  6:50 John Marvin
2000-11-22  7:56 ` Grant Grundler
2000-11-22 16:02 ` Paul Bame
2000-11-22  8:11 John Marvin
2000-11-22 19:55 ` Grant Grundler
2000-11-22 20:10   ` Kirk Bresniker

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=20001121113432.B883@parcelfarce.linux.theplanet.co.uk \
    --to=matthew@wil.cx \
    --cc=grundler@cup.hp.com \
    --cc=parisc-linux@puffin.external.hp.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