Re: [libxml-devel] Back

2008-07-03 Thread Trans
On Jul 3, 2:01 pm, Sean Chittenden <[EMAIL PROTECTED]> wrote: > git is demon spawn - don't get sucked into the ill-thought-out fad. I think that's a bit overstated. From what I understand the primary difference is the backend storage. Git stores an snapshot and Hg stores a delta. Perhaps Mackal

Re: [libxml-devel] Back

2008-07-03 Thread Dan Janowski
On Jul 3, 2008, at 14:01, Sean Chittenden wrote: Before we do that though I was wondering what others thought about of switching to Git? Well, I know git is the new cool think in town. But I'm on Windows, and love TortoiseSvn, so I don't have any motivation to move to git (lousy window

Re: [libxml-devel] Back

2008-07-03 Thread Sean Chittenden
Eventually, some sort of distributed source code management would be nice. I think it makes sense for open source projects for a lot of reasons. That being said, I think it is more important to use a SCM that is compatible with the environment of the current contributors. The revival of the gem by

[libxml-devel] [ libxml-Bugs-19738 ] malloc errors in libxml

2008-07-03 Thread noreply
Bugs item #19738, was opened at 2008-04-23 18:01 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=19738&group_id=494 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: malloc erro

[libxml-devel] [ libxml-Bugs-20117 ] Segfault when using XML::Reader.expand

2008-07-03 Thread noreply
Bugs item #20117, was opened at 2008-05-13 05:48 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=20117&group_id=494 Category: memory Group: v0.5 Status: Open Resolution: None Priority: 3 Submitted By: Gabriel Ebner (gebner) >Assigned to: Charlie Savage (cfis)

[libxml-devel] [ libxml-Bugs-7622 ] unknown XPath function causes SEGV

2008-07-03 Thread noreply
Bugs item #7622, was opened at 2007-01-05 23:10 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=7622&group_id=494 Category: None Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: Kouhei Sutou (kou) >Assigned to: Charlie Savage (cfis) Summa

[libxml-devel] [ libxml-Bugs-16214 ] SEGV when add the cloned/copied node

2008-07-03 Thread noreply
Bugs item #16214, was opened at 2007-12-10 08:29 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=16214&group_id=494 Category: memory Group: v0.5 >Status: Closed Resolution: None Priority: 4 Submitted By: Dan Janowski (danj) >Assigned to: Charlie Savage (cfis)

[libxml-devel] [ libxml-Bugs-9135 ] dup and clone methods cause segfaults

2008-07-03 Thread noreply
Bugs item #9135, was opened at 2007-03-08 12:38 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=9135&group_id=494 Category: None Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: Marc Munro (dbdude) >Assigned to: Charlie Savage (cfis) Summ

Re: [libxml-devel] Back

2008-07-03 Thread scollett
Eventually, some sort of distributed source code management would be nice. I think it makes sense for open source projects for a lot of reasons. That being said, I think it is more important to use a SCM that is compatible with the environment of the current contributors. The revival of the gem by

[libxml-devel] [ libxml-Bugs-8501 ] Building on Windows

2008-07-03 Thread noreply
Bugs item #8501, was opened at 2007-02-08 02:31 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=8501&group_id=494 Category: None Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: Charlie Savage (cfis) >Assigned to: Charlie Savage (cfis) Su

[libxml-devel] [ libxml-Bugs-7018 ] Parsing an empty string causes Segfault / Bus Error

2008-07-03 Thread noreply
Bugs item #7018, was opened at 2006-12-02 14:03 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=7018&group_id=494 Category: None Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: Nobody (None) >Assigned to: Charlie Savage (cfis) Summary: P

[libxml-devel] [ libxml-Bugs-19022 ] 0.5.3 Gem fails on Macintosh with "LoadError: no such file to load -- libxml_so"

2008-07-03 Thread noreply
Bugs item #19022, was opened at 2008-03-21 17:03 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=19022&group_id=494 Category: General Group: v0.5 >Status: Closed Resolution: None Priority: 3 Submitted By: Paul Legato (plegato) >Assigned to: Charlie Savage (cfi

[libxml-devel] [ libxml-Bugs-19258 ] Attribute nodes can be freed() twice.

2008-07-03 Thread noreply
Bugs item #19258, was opened at 2008-04-02 00:32 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=19258&group_id=494 Category: None Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: Joe Khoobyar (walltndr) >Assigned to: Charlie Savage (cfis

[libxml-devel] [ libxml-Bugs-20117 ] Segfault when using XML::Reader.expand

2008-07-03 Thread noreply
Bugs item #20117, was opened at 2008-05-13 05:48 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=20117&group_id=494 Category: memory Group: v0.5 >Status: Closed Resolution: None Priority: 3 Submitted By: Gabriel Ebner (gebner) Assigned to: Charlie Savage (cfis

[libxml-devel] [ libxml-Bugs-19242 ] xpath causes GC crash

2008-07-03 Thread noreply
Bugs item #19242, was opened at 2008-04-01 15:54 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=19242&group_id=494 Category: memory Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: Nobody (None) >Assigned to: Charlie Savage (cfis) Summar

[libxml-devel] [ libxml-Bugs-17885 ] Calling parse() twice causes segfault

2008-07-03 Thread noreply
Bugs item #17885, was opened at 2008-02-07 20:08 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=17885&group_id=494 Category: General Group: v0.5 >Status: Closed Resolution: None Priority: 3 Submitted By: Saurabh Nanda (saurabhnanda) >Assigned to: Charlie Sava

[libxml-devel] [ libxml-Bugs-19259 ] Calling remove! on a node causes memory leaks.

2008-07-03 Thread noreply
Bugs item #19259, was opened at 2008-04-02 00:33 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1971&aid=19259&group_id=494 Category: None Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: Joe Khoobyar (walltndr) >Assigned to: Charlie Savage (cfis

Re: [libxml-devel] Pushing libxml forward - a new 0.6.0 release

2008-07-03 Thread Sean Chittenden
As you might have guessed by the recent email traffic, I've dived into the libxml (and libxslt) ruby bindings since I need them MapBuzz. Charlie/MapBuzz FTW! Economic incentive == progress. Glad to hear you've been able to knock out these bugs. :~] -sc -- Sean Chittenden [EMAIL PROTECTE

Re: [libxml-devel] Back

2008-07-03 Thread Sean Chittenden
Before we do that though I was wondering what others thought about of switching to Git? Well, I know git is the new cool think in town. But I'm on Windows, and love TortoiseSvn, so I don't have any motivation to move to git (lousy windows support and no gui). I suppose it was easy to hav

Re: [libxml-devel] Back

2008-07-03 Thread Trans
On Jul 3, 1:15 pm, Charlie Savage <[EMAIL PROTECTED]> wrote: > Hi Trans, > > > Sorry I've been out of the loop for a bit. I've been working on some > > other projects. > > > I just emailed Charlie about working with him to get a new release > > out. How do we want to handle this? Should we tag th

Re: [libxml-devel] Back

2008-07-03 Thread Charlie Savage
Hi Trans, Sorry I've been out of the loop for a bit. I've been working on some other projects. I just emailed Charlie about working with him to get a new release out. How do we want to handle this? Should we tag the current version and allow the patches on trunk? Or create a branch and apply th

[libxml-devel] Back

2008-07-03 Thread Trans
Hi all, Sorry I've been out of the loop for a bit. I've been working on some other projects. I just emailed Charlie about working with him to get a new release out. How do we want to handle this? Should we tag the current version and allow the patches on trunk? Or create a branch and apply the pa