This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: version control system

From: fche at redhat dot com (Frank Ch. Eigler)
To: "Stone, Joshua I" <joshua dot i dot stone at intel dot com>
Cc: <systemtap at sources dot redhat dot com>
Date: Thu, 20 Sep 2007 16:40:35 -0400
Subject: Re: version control system
References: <20070914171342.GK31319@redhat.com> <16D5B9AB904B0B46B22A27002EE3A8C8E77681@scsmsx415.amr.corp.intel.com>

joshua.i.stone wrote:

> [...]  If we are willing to fully jump to DSCM, the I vote for git,
> but only because I haven't tried any others (mercurial, bazaar).

Well, why not give it a try.  The following URLs will all work to keep
roughly up-to-date with systemtap.  They contain only a periodically
git-cvsimported form of the src/ tree; the others (doc/, patches/)
would need their separate repos.

        git://sources.redhat.com/git/systemtap.git
        ssh://sources.redhat.com/git/systemtap.git
        http://sources.redhat.com/git/systemtap.git

While the "ssh:" URL can accept git push, let's not try that until
when/if we decide to switch over altogether.

> We could even run a git-cvsserver for the dinosaurs to use. :)

With sourceware being a machine shared amongst diverse projects, this
could be difficult.

- FChE

Follow-Ups:
- RE: version control system
  - From: Stone, Joshua I

References:
- version control system
  - From: Frank Ch. Eigler
- RE: version control system
  - From: Stone, Joshua I

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]