From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?R=C3=A9mi_Vanicat?= Subject: Re: Support (or not) for Emacs 21, and XEmacs Date: Fri, 16 Apr 2010 15:32:42 +0200 Message-ID: <87iq7rjzet.dlv@debian.org> References: <15649C3E-517D-433D-977F-06008C20A4F4@gmail.com> <87k4s7mtvk.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O2lfN-0007JH-Mo for emacs-orgmode@gnu.org; Fri, 16 Apr 2010 09:33:05 -0400 Received: from [140.186.70.92] (port=57273 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O2lfL-0007J9-Ji for emacs-orgmode@gnu.org; Fri, 16 Apr 2010 09:33:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O2lfJ-0001vH-Qx for emacs-orgmode@gnu.org; Fri, 16 Apr 2010 09:33:03 -0400 Received: from lo.gmane.org ([80.91.229.12]:35312) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O2lfJ-0001uu-LE for emacs-orgmode@gnu.org; Fri, 16 Apr 2010 09:33:01 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1O2lfH-00043E-Bp for emacs-orgmode@gnu.org; Fri, 16 Apr 2010 15:32:59 +0200 Received: from 88-136-167-220.adslgp.cegetel.net ([88.136.167.220]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 Apr 2010 15:32:59 +0200 Received: from vanicat by 88-136-167-220.adslgp.cegetel.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 Apr 2010 15:32:59 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Sebastian Rose writes: > * One git question: > > When I pulled, I got the message, that there is a new branch. But that > branch did not show up in the list `git branch' gives me. use git branch -r (or git branch -a) to list remote (or all branch) > Then I did: > sh$ git checkout origin/remove-compatibility-code better to create a locale branch tracking the remote one with: git checkout -b remove-compatibility-code origin/remove-compatibility-code Then git pull will work as expected. [...] > While this is all fine, and I'm on `remove-compatibility-code' now: will > that branch be updated when I pull the next time? Not with you described config. -- RĂ©mi Vanicat