unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: Joel James Adamson <adamsonj@email.unc.edu>
Cc: guile-user@gnu.org, Thien-Thi Nguyen <ttn@gnuvola.org>
Subject: Re: Plotting in Guile
Date: Wed, 4 Aug 2010 06:51:26 -0700 (PDT)	[thread overview]
Message-ID: <348699.64011.qm@web37901.mail.mud.yahoo.com> (raw)
In-Reply-To: <m3fwyu4j3e.fsf@chondestes.bio.unc.edu>

> From: Joel James Adamson <adamsonj@email.unc.edu>
>> Mike Gran <spk121@yahoo.com> writes:
> 

> >
> > It is at http://github.com/spk121/guile-plotutils

> 
> Can we set up something on github?  As soon as it's ready for Savannah
> we can have a mailing list there.
> 
> Joel

I made a space for it on github at http://github.com/spk121/guile-plotutils
My rough code is in there under the 'guile' directory.  It should be visible
now.  It works for me.

I'm not sure about setting up its own project on Savannah because I think
I can get it included in the main GNU Plotutils package, instead of making
its own separate formal GNU Guile-Plotutils project.  Philosophically,
Savannah doesn't seem to be the place for temporary disposable projects.

(I'm not opposed to putting it on Savannah, though.  I just don't want 
to clutter it up.  But maybe I worry too much about that sort of thing.)

I think if you make an account at github, I just add you to the repo, and you
can hack the code and the wiki as you like.  And when we have something
clean, we can submit it to the GNU Plotutils maintainer for possible
inclusion.

-Mike



  reply	other threads:[~2010-08-04 13:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 15:21 Plotting in Guile Joel James Adamson
2010-07-28 16:04 ` Hans Aberg
2010-07-28 17:54   ` Joel James Adamson
2010-07-28 18:26     ` Linas Vepstas
2010-07-28 18:43       ` Joel James Adamson
2010-07-29  6:52         ` Thien-Thi Nguyen
2010-07-29 14:59           ` Joel James Adamson
2010-07-29 15:14             ` Thien-Thi Nguyen
2010-07-29 17:34               ` Joel James Adamson
2010-07-28 18:45     ` Hans Aberg
2010-07-28 18:50       ` Joel James Adamson
2010-07-28 20:56         ` Hans Aberg
2010-07-29 18:57     ` Neil Jerram
2010-07-28 16:16 ` Mike Gran
2010-07-28 16:56   ` Joel James Adamson
2010-07-28 17:20     ` Mike Gran
2010-07-28 17:59       ` Joel James Adamson
2010-07-29  7:01   ` Thien-Thi Nguyen
2010-07-29 14:52     ` Joel James Adamson
2010-07-29 15:21       ` Thien-Thi Nguyen
2010-07-29 17:31         ` Joel James Adamson
2010-07-29 18:43           ` Thien-Thi Nguyen
2010-07-30  2:40     ` Mike Gran
2010-07-30 12:19       ` Thien-Thi Nguyen
2010-08-03 13:46         ` Mike Gran
2010-08-03 19:20           ` Thien-Thi Nguyen
2010-08-04  5:14             ` Mike Gran
2010-08-04 13:12               ` Joel James Adamson
2010-08-04 13:51                 ` Mike Gran [this message]
2010-08-04 15:21                   ` Joel James Adamson
2010-08-04 19:51                   ` Thien-Thi Nguyen
2010-08-15 22:49                   ` Ludovic Courtès
2010-08-18 15:37 ` Andy Wingo
2010-08-18 17:03   ` Joel James Adamson

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=348699.64011.qm@web37901.mail.mud.yahoo.com \
    --to=spk121@yahoo.com \
    --cc=adamsonj@email.unc.edu \
    --cc=guile-user@gnu.org \
    --cc=ttn@gnuvola.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).