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

On Tue, Nov 06, 2007 at 04:52:56PM +0000, Brian Gough wrote:
> 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).

Ah, too bad CVS doesn't have the concept of change sets. Imo, it's a 
reason alone to switch away from CVS.

> 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.

Imo, it has huge advantages over CVS:

 * change sets -> accurate checkpointing to any version

 * integrity is verified
	* no difference between binary and ascii files -> data is 
	  preserved exactly no matter what

 * branching and merging
	* merging actually preserves change history instead of hiding it
	* merging is fast and easy

 * VERY helpful logging utility (try log --stat and log -p)

 * patch generation (git format-patch)
	* authors are preserved (committer is separate)
	* change log messages are preserved
	* binary diffs: all files are patchable
	* easy distributed development

 * all repositories are mergeable among each other (distributed development)

 * it's quote fast.. I've been using git at work, and it beats SVN
   in almost all operations

-- 
Heikki Orsila			Barbie's law:
heikki.orsila@iki.fi		"Math is hard, let's go shopping!"
http://www.iki.fi/shd

  reply	other threads:[~2007-11-06 21:15 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
2007-11-06 21:15       ` Heikki Orsila [this message]
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=20071106211510.GC6105@jolt.modeemi.cs.tut.fi \
    --to=shd@modeemi.fi \
    --cc=bjg@gnu.org \
    --cc=gsl-discuss@sourceware.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).