From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Pascal Bourguignon Newsgroups: gmane.emacs.help Subject: Re: distributed revision control? Date: Sun, 05 Aug 2007 14:12:50 +0200 Organization: Informatimago Message-ID: <87lkcq2n99.fsf@voyager.informatimago.com> References: <1186283558.939662.293950@e16g2000pri.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1186317675 30546 80.91.229.12 (5 Aug 2007 12:41:15 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 5 Aug 2007 12:41:15 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Aug 05 14:41:14 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IHfPz-0001YU-4g for geh-help-gnu-emacs@m.gmane.org; Sun, 05 Aug 2007 14:41:14 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IHfPv-0006zG-JI for geh-help-gnu-emacs@m.gmane.org; Sun, 05 Aug 2007 08:41:07 -0400 Original-Path: shelby.stanford.edu!headwall.stanford.edu!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 47 Original-X-Trace: individual.net 4OYRrTEeJxgB67ew51/yuwK6GfnBVWCqwKbPFhpga6mtdqvAi7 Cancel-Lock: sha1:SlsaeoGEkpWnUj7jHIMOYOcPlhI= sha1:B686/te2PRo0p864ujL9O2+AD+U= Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA oElEQVR4nK3OsRHCMAwF0O8YQufUNIQRGIAja9CxSA55AxZgFO4coMgYrEDDQZWPIlNAjwq9 033pbOBPtbXuB6PKNBn5gZkhGa86Z4x2wE67O+06WxGD/HCOGR0deY3f9Ijwwt7rNGNf6Oac l/GuZTF1wFGKiYYHKSFAkjIo1b6sCYS1sVmFhhhahKQssRjRT90ITWUk6vvK3RsPGs+M1RuR mV+hO/VvFAAAAABJRU5ErkJggg== X-Accept-Language: fr, es, en X-Disabled: X-No-Archive: no User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.94 (gnu/linux) Original-Xref: shelby.stanford.edu gnu.emacs.help:150759 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:46330 Archived-At: knubee writes: > A colleague and I want to work on some shared documents via tramp and > revision control. The issue: we do not have access to a shared > location that could serve as a centralized repository. (Our project > isn't an open source software project and doesn't warrant such things > as sourceforge etc. We tried google projects but couldn't see a way to > integrate this with emacs version control.) > > Reading about "distributed revision control systems" (DRCS) suggests > this may be the way to go. However, most of the information we have > found suggests that although individuals can work independently on > their local versions, there is an assumption that at some point > changes are committed to a single repository. > > The model we would like to pursue is that the local version of one of > us exists as the main repository. So, one approach is" "committing" to > that repository would take the form of something more like email than > ftp/ssh access to a machine with a repository. (We are also open to > other approaches) > > Does anyone here know if Arch or Bazaar-NG (or something else we could > use from within emacs) support such a model? If so, any pointers to > how to do this? > > (Sorry if this post is off topic. If there is a more appropriate list > that deals with revision control systems available within emacs, > please let me know.) > > thanks. > darcs is designed to deal with this problem. Technically, there is no central repository in darcs, all the sandboxes are branches. Changes are not commited to any central repository, but at one point, you may want to send your patches to the other guys, and vice versa. If you're only two, it's ok; if you're more, it's easier if there is a single central integrator. -- __Pascal Bourguignon__ http://www.informatimago.com/ THIS IS A 100% MATTER PRODUCT: In the unlikely event that this merchandise should contact antimatter in any form, a catastrophic explosion will result.