From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: tomas@tuxteam.de Newsgroups: gmane.emacs.devel Subject: Re: bzr repository ready? Date: Sat, 28 Nov 2009 07:45:39 +0100 Message-ID: <20091128064539.GB2575@tomas> References: <87zl6crij4.fsf@red-bean.com> <87hbsifdsr.fsf@telefonica.net> <87d435sn0b.fsf@uwakimon.sk.tsukuba.ac.jp> <87hbsgc4l8.fsf@telefonica.net> <83ocmnnc5d.fsf@gnu.org> <877htbaitb.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1259391159 19536 80.91.229.12 (28 Nov 2009 06:52:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 28 Nov 2009 06:52:39 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 28 07:52:32 2009 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 1NEHAU-0004E4-Vy for ged-emacs-devel@m.gmane.org; Sat, 28 Nov 2009 07:52:31 +0100 Original-Received: from localhost ([127.0.0.1]:59707 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NEHAU-00047f-He for ged-emacs-devel@m.gmane.org; Sat, 28 Nov 2009 01:52:30 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NEHAL-00045v-Em for emacs-devel@gnu.org; Sat, 28 Nov 2009 01:52:21 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NEHAF-00044D-Hj for emacs-devel@gnu.org; Sat, 28 Nov 2009 01:52:19 -0500 Original-Received: from [199.232.76.173] (port=49567 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NEHAF-00044A-2I for emacs-devel@gnu.org; Sat, 28 Nov 2009 01:52:15 -0500 Original-Received: from alextrapp1.equinoxe.de ([217.22.192.104]:34379 helo=www.elogos.de) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NEHAE-00081I-J7 for emacs-devel@gnu.org; Sat, 28 Nov 2009 01:52:14 -0500 Original-Received: by www.elogos.de (Postfix, from userid 1000) id F04ED90048; Sat, 28 Nov 2009 07:45:39 +0100 (CET) Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.15+20070412 (2007-04-11) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:117898 Archived-At: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Nov 27, 2009 at 08:22:31PM +0100, Lennart Borgman wrote: [...] > Hum. That seems pretty important even though I am pretty sure I do not > understand all the details. The principle is quite easy (although details can get messy, as always): if you have other people depending on your (published) repository, you better always "move forward" and don't mess with the past (and rebasing is a mild way of messing with the past). Otherwise "your" past and "your client's past" won't agree, and that isn't funny. > But why are not normal human beeings protected from the evil of > rebase? Why do they have to know about it? Because when you are developing a local patch derived from some upstream, rebase is too convenient to ignore it. It lets you "see" your changes always relative to the "current upstream version" ("as if" you started developing from there -- and that's the "history changing" bit). To sum it up -- you may practice revisionism whenever nobody's looking. Regards - -- tom=C3=A1s -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFLEMcTBcgs9XrR2kYRAnjjAJ40E+aDcLAO99oc5E9P7m2L+9n+HACfbFrH De3zaiZBC4HnjZRbR70mZRg=3D =3DOVZ4 -----END PGP SIGNATURE-----