[GRASS-dev] Cairo monitor driver

[Soeren Gebbert]

Hi,
JFYI i have created a git repository of grass from the latest cvs version
to manage my grass code.  Now i have a local copy
of the grass cvs (my own grass branch) using git and i'm able commit, update
and diff
code and new files to my branch
without read or write access to the grass cvs repository. And this is really
nice. :)
And i'm able to commit the code later to cvs.

Using git you can even check in code without an internet access
having all the log data and history on your local disk.

The git repository is located here:
http://www-pool.math.tu-berlin.de/~soeren/grass/files/grass.git.tar.bz2
so everybody who is interested in using a nice SCM to manage there code
without access to the grass cvs can use it.

Here is an introduction from Linus into git (be aware, many of us are stupid
and ugly in his eyes ;) ):
http://www.youtube.com/watch?v=4XpnKHJAok8

This is a short introduction into git and cvs:
http://www.kernel.org/pub/software/scm/git/docs/tutorial.html
http://issaris.blogspot.com/2005/11/cvs-to-git-and-back.html
http://www.kernel.org/pub/software/scm/git/docs/cvs-migration.html

I hope this helps a bit to manage local grass copies.
Best regards
Soeren


2007/10/15, Carlos Guâno Grohmann <carlos.grohmann at gmail.com>:
>
> Can you give some examples of the usage? (not the final product, but
> the commands)
>
> thanks
>
> Carlos
>
>
>
> On 10/15/07, Lars Ahlzen <lars at ahlzen.com> wrote:
> > Brad Douglas wrote:
> > >>> I can of course post code too, if anyone would be interested in
> actually
> > >>> trying it.
> > >> The code would certainly be useful.
> > >
> > > +1
> >
> > The source is up! Sorry about the delay.
> >
> > I do realize that this is not the ideal format. A patch against the
> > current 6.3 CVS tree would probably have been better, but apparently CVS
> > doesn't let you add files even to your local copy without write access
> > to the repository... oh well..
> >
> > Anyhow, the code along with brief build and usage instructions are
> > available at:
> >
> > http://lars.ahlzen.com/cairograss/
> >
> > The makefiles are a bit of a hack and need to be fixed. Hopefully
> > they'll work, though. And the code in general is, as previously
> > mentioned, experimental. But it can always be cleaned up if it seems
> > worthwhile.
> >
> > Feel free to try it out, and let me know if (when?) you run into
> > problems building or using it, or if you have any other feedback!
> >
> > I don't know what the policy is for posting experimental code like this
> > to the patch tracker, so given its current state I opted for not doing
> > this. Let me know if I should.
> >
> > / Lars
> >
> > --
> > Lars Ahlzen
> > lars at ahlzen.com
> >
> > _______________________________________________
> > grass-dev mailing list
> > grass-dev at grass.itc.it
> > http://grass.itc.it/mailman/listinfo/grass-dev
> >
>
>
> --
> +-----------------------------------------------------------+
>               Carlos Henrique Grohmann - Guano
>   Visiting Researcher at Kingston University London - UK
>   Geologist M.Sc  - Doctorate Student at IGc-USP - Brazil
> Linux User #89721  - carlos dot grohmann at gmail dot com
> +-----------------------------------------------------------+
> _________________
> "Good morning, doctors. I have taken the liberty of removing Windows
> 95 from my hard drive."
> --The winning entry in a "What were HAL's first words" contest judged
> by 2001: A SPACE ODYSSEY creator Arthur C. Clarke
>
> Can't stop the signal.
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-dev/attachments/20071016/5692e47a/attachment.html