public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gough <bjg@gnu.org>
To: Heikki Orsila <shd@modeemi.fi>
Cc: gsl-discuss@sourceware.org
Subject: Re: On GSL version control
Date: Tue, 06 Nov 2007 16:53:00 -0000	[thread overview]
Message-ID: <87mytr5n9z.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <20071106115753.GB6105@jolt.modeemi.cs.tut.fi>

At Tue, 6 Nov 2007 13:57:53 +0200,
Heikki Orsila wrote:
> 
> Hello. I just converted GSL CVS repo into Git to advertise possibilities 
> of using Git for GSL development. I'm only a newbie on GSL, but I think 
> any GSL developer would benefit from a system better than CVS.

Thanks for your email.  I've been trying git out myself in recent
weeks, and considering whether it is viable (for moving the repository
to Savannah.gnu.org).

As you probably know, they have recently added support for git, with
simultaneous CVS read-only checkouts - which is useful for people who
don't want to switch from CVS.

I hit a few problems in the conversion process - for example, you'll
find there is a stray file sum/gsl_sf_sum.h in HEAD which should not
be there.

It is caused by cvsps putting some patches in incorrect order -- with
later versions of the file coming before earlier versions (a
workaround is to use the cvsps -z 60 option to reduce the patch time
window).

Git certainly has some advantages over CVS - the main one in my
opinion is the ability to verify the integrity of the repository from
the top-level SHA checksum.

-- 
Brian Gough

  reply	other threads:[~2007-11-06 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05  8:57 gsl_sf_bessel_jl_e error in CVS Giulio Bottazzi
2007-11-05 14:59 ` Brian Gough
2007-11-06 11:58   ` On GSL version control Heikki Orsila
2007-11-06 16:53     ` Brian Gough [this message]
2007-11-06 21:15       ` Heikki Orsila
2007-11-06 22:26       ` Gerard Jungman
2007-11-06 23:13         ` Heikki Orsila
2007-11-07 19:43         ` Brian Gough

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

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

  git send-email \
    --in-reply-to=87mytr5n9z.wl%bjg@network-theory.co.uk \
    --to=bjg@gnu.org \
    --cc=gsl-discuss@sourceware.org \
    --cc=shd@modeemi.fi \
    /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).