From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Bolle Subject: Re: Git terminology: remote, add, track, stage, etc. Date: Fri, 22 Oct 2010 22:16:25 +0200 Message-ID: <1287778585.2025.14.camel@localhost.localdomain> References: <8835ADF9-45E5-4A26-9F7F-A72ECC065BB2@gmail.com> <8B950268-7F6E-40E5-9D6C-F150EBEA4F0C@wincent.com> <6FCE62E3-A27E-43D6-9FDF-0133ABD851C2@wincent.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Wincent Colaiuta , Miles Bader , Matthieu Moy , Thore Husfeldt , git@vger.kernel.org To: Eugene Sajine X-From: git-owner@vger.kernel.org Fri Oct 22 22:30:24 2010 Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1P9OFq-0002fk-QF for gcvg-git-2@lo.gmane.org; Fri, 22 Oct 2010 22:30:23 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755905Ab0JVUaP (ORCPT ); Fri, 22 Oct 2010 16:30:15 -0400 Received: from smtp-out2.tiscali.nl ([195.241.79.177]:53381 "EHLO smtp-out2.tiscali.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753087Ab0JVUaO (ORCPT ); Fri, 22 Oct 2010 16:30:14 -0400 X-Greylist: delayed 824 seconds by postgrey-1.27 at vger.kernel.org; Fri, 22 Oct 2010 16:30:14 EDT Received: from [212.123.169.34] (helo=[192.168.1.99]) by smtp-out2.tiscali.nl with esmtp (Exim) (envelope-from ) id 1P9O2P-0006Bo-PT; Fri, 22 Oct 2010 22:16:29 +0200 In-Reply-To: X-Mailer: Evolution 2.91.1 (2.91.1-1.fc15) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Tue, 2010-10-19 at 11:09 -0400, Eugene Sajine wrote: > There should be some different consistent and not inter-crossing > naming for the origin's master branch (on the remote side), for the > local origin/master and for local master that is a tracking branch. > The only way i found so far to explain this is actually via the naming > syntax where having / in the name of the branch means remote branch. I > was a bit surprised that i can create a local branch with a slash in > the name - probably it should be prohibited. Allowing local branches with a slash in their name is a feature I use heavily. Ie, in general my local repositories use this scheme: $ git branch * master $BRANCH_F00 $USER/$TOPIC_FOO $USER/$TOPIC_BAR [...] $USER/$TOPIC_BAZ This makes it trivial to quickly distinguish my (local) work from other people's (remote) work. Does the benefit of naming clarity justify prohibiting that scheme? Paul Bolle