From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: What a modern collaboration toolkit looks like Date: Sun, 06 Jan 2008 03:09:19 -0500 Message-ID: References: <20071230122217.3CA84830B9A@snark.thyrsus.com> <20071231130712.GB8641@thyrsus.com> <87y7b96az8.fsf@member.fsf.org> <87fxxfnrhi.fsf@catnip.gol.com> <85abnkodlu.fsf@lola.goethe.zz> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1199607321 28998 80.91.229.12 (6 Jan 2008 08:15:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 6 Jan 2008 08:15:21 +0000 (UTC) Cc: tassilo@member.fsf.org, emacs-devel@gnu.org, miles@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 06 09:15:42 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JBQfV-0001Fs-PB for ged-emacs-devel@m.gmane.org; Sun, 06 Jan 2008 09:15:42 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBQf8-0002GZ-Q5 for ged-emacs-devel@m.gmane.org; Sun, 06 Jan 2008 03:15:18 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBQeP-0001YP-2Z for emacs-devel@gnu.org; Sun, 06 Jan 2008 03:14:33 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBQeN-0001Wi-Tq for emacs-devel@gnu.org; Sun, 06 Jan 2008 03:14:32 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBQeN-0001WN-O3 for emacs-devel@gnu.org; Sun, 06 Jan 2008 03:14:31 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JBQeN-0004K1-O2; Sun, 06 Jan 2008 03:14:31 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1JBQZL-0001Wi-UB; Sun, 06 Jan 2008 03:09:19 -0500 In-reply-to: <85abnkodlu.fsf@lola.goethe.zz> (message from David Kastrup on Sat, 05 Jan 2008 09:55:57 +0100) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:86294 Archived-At: > It sounds like "git push" is the real analogue of CVS commit, No. Pushing works between repositories. It is the way to propagate changes to others. At this level, that's just a detail. The must important thing about CVS commit is that it alters what other people will get if they ask to get the current version from the repository. With git, the operation which does that is `push'. > CVS GIT > save file = commit No. Saving a file will not give you all the version control history and tools and diffs and branching and other tools that committing does under git. Ok, but those are details. The crucial point is that saving a file, or git commit, alters your own data only; it does not affect what other users will get from the published repository.