Gentoo on ppc with GXT6500P Gfx? Post: 302341151

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Rogue PPC RPm

Hello, i need to Rogue RPm for PPC, anybody knows where i can get it? Thanks. i am new to Unix, thats why ia m postin here. Thank you!

2. Linux

hi guys, i have just installed Redhat Linux 8 on my home computer and it doesn't have the valid driver for my Radeon 9800 xt have looked about for it and can't find the driver. My computer works fine in a way, i can use it, but it would just be nice to have it set up fully correct so i can...

3. Ubuntu

Which GFX driver version am I'm using under Ubuntu 7.04?

I just did a fresh install of Ubuntu 7.04 with a Gnome desktop. Following some instructions on the ATI site I think I just managed to install 8.36.5 of the drivers for my Radeon 9500, I'm getting a "Proprietary Drivers in use" warning icon at the top right of the screen, which I activated with...

4. Red Hat

Fedora 12 on PPC

I'm trying to install a linux system on a IBM PowerPC 275 system. I noticed that fedora 12 supports PowerPC. Does anyone have experience with this? I don't want to pay the fee for an enterprise licence for red hat or suse.

5. Solaris

Issues after moving gfx card

Hello, I have a Sun V880 and a raptor gfx -8p today i installed a lsi card and had to use the pci slot that the gfx was using as it needed a 5v rail, after doing so i did a reconfigure boot with boot -r and now i no longer have a functioning display Im probably missing something simple,...

LEARN ABOUT DEBIAN

git-cherry

GIT-CHERRY(1)							    Git Manual							     GIT-CHERRY(1)

NAME

       git-cherry - Find commits not merged upstream

SYNOPSIS

       git cherry [-v] [<upstream> [<head> [<limit>]]]

DESCRIPTION

       The changeset (or "diff") of each commit between the fork-point and <head> is compared against each commit between the fork-point and
       <upstream>. The commits are compared with their patch id, obtained from the git patch-id program.

       Every commit that doesn't exist in the <upstream> branch has its id (sha1) reported, prefixed by a symbol. The ones that have equivalent
       change already in the <upstream> branch are prefixed with a minus (-) sign, and those that only exist in the <head> branch are prefixed
       with a plus (+) symbol:

		      __*__*__*__*__> <upstream>
		     /
	   fork-point
		     \__+__+__-__+__+__-__+__> <head>

       If a <limit> has been given then the commits along the <head> branch up to and including <limit> are not reported:

		      __*__*__*__*__> <upstream>
		     /
	   fork-point
		     \__*__*__<limit>__-__+__> <head>

       Because git cherry compares the changeset rather than the commit id (sha1), you can use git cherry to find out if a commit you made locally
       has been applied <upstream> under a different commit id. For example, this will happen if you're feeding patches <upstream> via email
       rather than pushing or pulling commits directly.

OPTIONS

       -v
	   Verbose.

       <upstream>
	   Upstream branch to compare against. Defaults to the first tracked remote branch, if available.

       <head>
	   Working branch; defaults to HEAD.

       <limit>
	   Do not report commits up to (and including) limit.

SEE ALSO

       git-patch-id(1)

GIT

       Part of the git(1) suite

Git 1.7.10.4							    11/24/2012							     GIT-CHERRY(1)

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Rogue PPC RPm

Discussion started by: Ro'Taygahn

2. Linux

Redhat Linux 8 gfx card prob

Discussion started by: SemperFi