From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Emacs branches in git Date: Mon, 17 Feb 2014 01:53:00 +0200 Message-ID: <87txbyd38j.fsf@yandex.ru> References: <3188.1392526217@olgas.newt.com> <87eh33irbn.fsf@yandex.ru> <87eh32rf64.fsf@olgas.newt.com> <877g8ux15e.fsf@fencepost.gnu.org> <878utapu6p.fsf@olgas.newt.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1392594796 11781 80.91.229.3 (16 Feb 2014 23:53:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 16 Feb 2014 23:53:16 +0000 (UTC) Cc: emacs-devel@gnu.org To: Bill Wohler Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 17 00:53:25 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WFBWW-0008Dj-W3 for ged-emacs-devel@m.gmane.org; Mon, 17 Feb 2014 00:53:25 +0100 Original-Received: from localhost ([::1]:35520 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFBWW-0006Xm-Hj for ged-emacs-devel@m.gmane.org; Sun, 16 Feb 2014 18:53:24 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51819) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFBWP-0006Xh-QS for emacs-devel@gnu.org; Sun, 16 Feb 2014 18:53:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WFBWK-0008DW-T9 for emacs-devel@gnu.org; Sun, 16 Feb 2014 18:53:17 -0500 Original-Received: from mail-ee0-x232.google.com ([2a00:1450:4013:c00::232]:56447) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFBWK-0008DR-Ls for emacs-devel@gnu.org; Sun, 16 Feb 2014 18:53:12 -0500 Original-Received: by mail-ee0-f50.google.com with SMTP id d17so6689502eek.37 for ; Sun, 16 Feb 2014 15:53:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version:content-type; bh=mNJUhInGvb7NE3ju9Mbk1Ia3DLYRon6f3iMRl0xVYs8=; b=QNQXeoDkyOKEO242s2I0CuWu5v6hrwDcHj/33nhZEyEy/b1yRS0x+HKxhKFwFZiB7+ u86MCQIm/Si+OcHOSN9Rvx6DEl6ky4+t1W0f4Bw1qZUGcUftgg4a/wLdLpktwVP/Cc5o U8uwC2mpXL4FFOiKiZqXUITcpx/QgIIusPTJ2TPhEOzujDvYY7MVRtlgv1eSb1mlKeIO 5uoJbKYoiz1D98j4OzqhWcvJlHRb1xa017iUOSk8BW2tI5UDJMdwiUfzFLEWHJ3WE4Du eWjz69Svekcsx8n4nN9JnNYg/Hnktj3zRsoolGJXCsGU72cRpp8LbvNF6plkYWtSfy4+ plbw== X-Received: by 10.14.105.200 with SMTP id k48mr23648921eeg.44.1392594791679; Sun, 16 Feb 2014 15:53:11 -0800 (PST) Original-Received: from axl ([93.109.195.252]) by mx.google.com with ESMTPSA id x6sm50464929eew.20.2014.02.16.15.53.09 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 16 Feb 2014 15:53:10 -0800 (PST) In-Reply-To: <878utapu6p.fsf@olgas.newt.com> (Bill Wohler's message of "Sun, 16 Feb 2014 14:30:06 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c00::232 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:169673 Archived-At: Bill Wohler writes: >>> Please see http://nvie.com/posts/a-successful-git-branching-model/ for >>> the rationale. I don't see any justification there, except "We consider origin/master to be ... a production-ready state." Which is just an arbitrary opinion. >>> Also, in git, release branches are deleted when they are >>> no longer needed. So what? Tags can live on. >> You are talking past each other. You want to organize tags into a >> directory of tags, > > s/tags/branches/ ?? >> Dmitry is talking about placing tags all into a >> single branch. Which makes very little sense. If master is to be used "for tagged releases", all release-tagged revisions have to be able to line up in one branch. Interspersed with plain revisions, of course. > Except that's not the point, but rather a side-effect. The point is that > master holds the production-ready commits. Yes, and why do we need that? If one wants to use the latest release, they can just fetch the list of tags, and then checkout the one with the greatest number. >> But it's not obvious to >> casual users of gits that you can have tags in a directory structure >> that has nothing to do with either the work directory or the commit >> tree. > > Can you expound on that? Yes, please.