From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Angelo Graziosi Newsgroups: gmane.emacs.devel Subject: Re: Move to git is imminent - awaiting Stefan's approval Date: Tue, 07 Jan 2014 11:24:12 +0100 Message-ID: <52CBD5CC.4020804@alice.it> References: <52CB2AB0.4080505@alice.it> <877gachfza.fsf@igel.home> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1389090273 18747 80.91.229.3 (7 Jan 2014 10:24:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 7 Jan 2014 10:24:33 +0000 (UTC) Cc: emacs To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 07 11:24:38 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 1W0Tpu-0003IN-2y for ged-emacs-devel@m.gmane.org; Tue, 07 Jan 2014 11:24:38 +0100 Original-Received: from localhost ([::1]:39682 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0Tpt-0002v0-KV for ged-emacs-devel@m.gmane.org; Tue, 07 Jan 2014 05:24:37 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58151) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0Tpm-0002us-Tz for emacs-devel@gnu.org; Tue, 07 Jan 2014 05:24:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W0Tph-00061z-JD for emacs-devel@gnu.org; Tue, 07 Jan 2014 05:24:30 -0500 Original-Received: from smtp202.alice.it ([82.57.200.98]:39009) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0Tph-00061m-7c for emacs-devel@gnu.org; Tue, 07 Jan 2014 05:24:25 -0500 Original-Received: from [192.168.1.100] (87.12.223.137) by smtp202.alice.it (8.6.060.28) (authenticated as angelo.graziosi@alice.it) id 529A568805E48862; Tue, 7 Jan 2014 11:24:21 +0100 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: <877gachfza.fsf@igel.home> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 82.57.200.98 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:167584 Archived-At: Il 07/01/2014 0.01, Andreas Schwab ha scritto: > Angelo Graziosi writes: > >> Now trying >> >> $ git clone git://git.savannah.gnu.org/emacs.git emacs.git >> >> >> I don't get any revision number.. So in my future bug report how the trunk >> will be identified? > > A good way to identify a git branch is to use git describe. However it > prefers to have an annotated (release) tag available to base on, which > we currently don't have (bzr doesn't have the concept of annotated > tags). > >> Beside this, my local copy of BZR repository has dimension >> >> $ du -s emacs-trunk/ >> 126M emacs-trunk/ >> >> instead the git repository has dimension >> >> $ du -s emacs.git/ >> 1.1G emacs.git/ > > By default git downloads the history of all branches. You can use > --single-branch to only clone a single branch. This is the default if > you create a shallow clone. David Kastrup wrote: > For the build? No. git clone has the following options: > > --depth ... > --[no-]single-branch ... OK, trying $ git clone --single-branch git://git.savannah.gnu.org/emacs.git emacs.git the local repository has dimension 1.1G, so probably I need a more explicit example... Instead, trying $ git clone --depth 1 git://git.savannah.gnu.org/emacs.git emacs.git the local repository has dimension 160M which is a little greater than my current BZR (checkout --lightweight) repository (126M), but acceptable... Suppose now I want identify which "revision" introduced a bug. I am able to do this with a binary search using the BZR command $ bzr up -r ARG How can I do this with the "minimal" clone done with GIT? I hope someone creates a Wiki page with all these doubts clarified with explicit examples... :-) Thanks, Angelo.