From: Matthew Wilcox <matthew@wil.cx>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Alexey Dobriyan <adobriyan@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org, torvalds@osdl.org, seb@highlab.com
Subject: Re: -git11 breaks parisc and sh even more
Date: Wed, 14 Sep 2005 06:50:14 -0600 [thread overview]
Message-ID: <20050914125014.GA16698@parisc-linux.org> (raw)
In-Reply-To: <20050914091722.GA27148@colo.lackof.org>
On Wed, Sep 14, 2005 at 03:17:22AM -0600, Grant Grundler wrote:
> Looks like parisc/kernel/drivers.c is out of sync with the
> parisc-linux.org CVS tree. The p-l.o tree doesn't define "next_dev()"
> in drivers.c. It might be obvious to willy what's up here.
> ISTR he wanted to sync up tomorrow with linus again anyway.
> Willy?
The parisc tree hasn't been merged with Linus in a long time because I
find git completely impossible to use. The howtos are all out of date
and contradict each other. They don't tell me what I need to know.
Everybody who uses them has their own collection of private scripts that
work around the worst misfeatures. It's a complete fucking disaster.
The Debian cogito package doesn't have half the tools mentioned in the
howtos, as well as being months out of date. Last time I had the energy
to fight with it, it didn't even support pack files.
I'd love to stop using CVS and just use git. But it simply doesn't work.
next prev parent reply other threads:[~2005-09-14 12:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 17:47 -git11 breaks parisc and sh even more Alexey Dobriyan
2005-09-13 18:57 ` Sam Ravnborg
2005-09-13 20:37 ` Alexey Dobriyan
2005-09-13 20:39 ` Sam Ravnborg
2005-09-14 7:42 ` Grant Grundler
2005-09-14 7:43 ` Ingo Molnar
2005-09-14 7:44 ` Ingo Molnar
2005-09-14 9:17 ` Grant Grundler
2005-09-14 12:50 ` Matthew Wilcox [this message]
2005-09-14 14:52 ` Linus Torvalds
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=20050914125014.GA16698@parisc-linux.org \
--to=matthew@wil.cx \
--cc=adobriyan@gmail.com \
--cc=grundler@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=seb@highlab.com \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.