X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/
Message-ID: <1356134637.7821.10.camel@localhost>
Subject: Re: [geda-user] Find rat lines - summary
From: Peter Clifton <pcjc2 AT cam DOT ac DOT uk>
To: geda-user AT delorie DOT com
Date: Sat, 22 Dec 2012 00:03:57 +0000
In-Reply-To: <20121221232023.GA2329@visitor2.iram.es>
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1212150453530 DOT 26605 AT igor2priv>
	 <CAN0Jx-8mr2XmLHr7AzcTygk205H1H4_X1Y9VcQHw3zia5eGynQ AT mail DOT gmail DOT com>
	 <CAN-_CWyXNvnumf5OC+m-xRV0zMf3cCvyzLU3be_pC8DkNVZG0Q AT mail DOT gmail DOT com>
	 <1355861174 DOT 13534 DOT 14 DOT camel AT localhost>
	 <20121220101819 DOT GA26060 AT visitor2 DOT iram DOT es>
	 <1356003432 DOT 4776 DOT 10 DOT camel AT localhost>
	 <20121220122149 DOT GB20493 AT visitor2 DOT iram DOT es>
	 <1356100339 DOT 17857 DOT 0 DOT camel AT localhost>
	 <20121221173921 DOT GA25742 AT visitor2 DOT iram DOT es>
	 <1356128362 DOT 2796 DOT 3 DOT camel AT localhost>
	 <20121221232023 DOT GA2329 AT visitor2 DOT iram DOT es>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.6.2-0ubuntu2 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> > > I was just trying but had a problem. Cloning the repository worked but:
> > > 
> > > git checkout for_master origin/for_master
> > > 
> > > as you said in a previous message failed!
> > 
> > What was the error message?
> 
> error: pathspec 'for_master' did not match any file(s) known to git.
> error: pathspec 'origin/for_master' did not match any file(s) known to git.


I think I should have said:

git checkout -b for_master origin/master

(create a branch named "for_master" starting with commit
"origin/master").

 
> > What branches are listed with 
> > 
> > git branch
> 
> * pcb+gl

Ok, I couldn't remember what my repo.or.cz repository defaults to as
HEAD.

pcb+gl should be ok to use, gives you some board-outline rendering
stuff, a completely replaced GL polygon rasteriser (modified from
cairo), and generally should be a little faster. (But cleanly coded
enough to be pushed upstream yet).

pcb+gl_experimental is faster still, but contains even wackier code.
That branch uses GLSL shaders and vertex buffers etc.., so is nice and
quick - but it doesn't fallback gracefully if your OpenGL driver doesn't
support something it relies upon.

(Almost all cards and drivers do support what it needs).


> I'm using git 1.7.10.4, the one from Debian testing updated about 1 month
> ago. Apparently I could simply type git checkout origin/for_master.

Yes, it probably gets you into either a "detached head" state, where
you're not really on a branch.

OR.. into a place where you are on the "origin/for_master" branch, where
you should not actually make commits... or risk messing up your
repository's tracking of my remote repository.

> 41 files changed, 7430 insertions(+), 522 deletions(-)
> 
> from diffstat.

Yes, prototype first, refactor later...

The pcb+gl branch has a clone of almost the entire draw.c rendering code
embedded in src/hid/gtk/gtkhid-gl.c

I'm slowly working on figuring out what changes I required in that
branch (for 3D board-stack view etc.), and trying to refactor the git
HEAD draw.c code such that I can make those extensions.)

> > Nice.. I'll have to make it a little bit more configurable, and figure
> > out whether the "FOUND" flag should be applied to every object, or just
> > the connected ones..., then I can push it.
> 
> I believe that it should be applied to every object.

That isn't how it is currently implemented, but I am leaning towards
that view - out of risk of breaking anything people liked to do with
that flag in the past.

I know DJ uses "select found objects" after the "f" shortcut, so I need
to fix that to un-break his use-case.

Regards,

-- 
Peter Clifton <peter DOT clifton AT clifton-electronics DOT co DOT uk>

Clifton Electronics