From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Move to git is imminent - awaiting Stefan's approval Date: Mon, 06 Jan 2014 23:57:19 +0100 Organization: Organization?!? Message-ID: <871u0kvhv4.fsf@fencepost.gnu.org> References: <52CB2AB0.4080505@alice.it> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1389049061 25170 80.91.229.3 (6 Jan 2014 22:57:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 6 Jan 2014 22:57:41 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 06 23:57:48 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 1W0J7C-0006jr-T1 for ged-emacs-devel@m.gmane.org; Mon, 06 Jan 2014 23:57:47 +0100 Original-Received: from localhost ([::1]:37991 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0J7C-0006iD-Jj for ged-emacs-devel@m.gmane.org; Mon, 06 Jan 2014 17:57:46 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35970) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0J75-0006gt-9w for emacs-devel@gnu.org; Mon, 06 Jan 2014 17:57:44 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W0J6z-0008Sk-VH for emacs-devel@gnu.org; Mon, 06 Jan 2014 17:57:39 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:39395) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0J6z-0008SX-Od for emacs-devel@gnu.org; Mon, 06 Jan 2014 17:57:33 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1W0J6x-0006F3-K3 for emacs-devel@gnu.org; Mon, 06 Jan 2014 23:57:31 +0100 Original-Received: from x2f5214e.dyn.telefonica.de ([2.245.33.78]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 06 Jan 2014 23:57:31 +0100 Original-Received: from dak by x2f5214e.dyn.telefonica.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 06 Jan 2014 23:57:31 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 81 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: x2f5214e.dyn.telefonica.de X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:Ns3T0iVVKkvxa6Xdvw3qwXjkUEY= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:167537 Archived-At: Angelo Graziosi writes: > Usually I build emacs trunk weekly. My local copy of trunk has been > created, the first time, with > > $ bzr checkout --lightweight http://bzr.savannah.gnu.org/r/emacs/trunk > emacs-trunk > > > and then updating "daily" it with > > $ cd emacs-trunk > $ bzr up "lightweight" > When I find a problem ("bug"), I flag it to this list saying something > like this > > "In trunk rev. 115890 there is this problem... BLA BLA BLA..." > > > 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? The commit ids are unique. It's usually easiest to quote the entire SHA128 via copy&paste, but the first 16 digits or so are usually sufficient. > Beside this, my local copy of BZR repository has dimension > > $ du -s emacs-trunk/ > 126M emacs-trunk/ "lightweight" > instead the git repository has dimension > > $ du -s emacs.git/ > 1.1G emacs.git/ > > it contains an emacs.git/.git directory of about 930M which probably > doesn't need for the Emacs build (bootstrap). For the build? No. git clone has the following options: --depth Create a shallow clone with a history truncated to the specified number of revisions. A shallow repository has a number of limitations (you cannot clone or fetch from it, nor push from nor into it), but is adequate if you are only interested in the recent history of a large project with a long history, and would want to send in fixes as patches. --[no-]single-branch Clone only the history leading to the tip of a single branch, either specified by the --branch option or the primary branch remote’s HEAD points at. When creating a shallow clone with the --depth option, this is the default, unless --no-single-branch is given to fetch the histories near the tips of all branches. Further fetches into the resulting repository will only update the remote-tracking branch for the branch this option was used for the initial cloning. If the HEAD at the remote did not point at any branch when --single-branch clone was made, no remote-tracking branch is created. In addition, once you have a local repository, something like git clone existing_workdir new_workdir will do the cloning by using hard links, taking almost no time and no space. I often do that for one-off testing of stuff while my "main" workdir is busy compiling stuff. -- David Kastrup