From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Steinar Bang Newsgroups: gmane.emacs.devel Subject: Re: A simple git workflow for the rest of us Date: Sat, 22 Nov 2014 16:00:30 +0100 Organization: Probably a good idea Message-ID: <87ioi72sc1.fsf@dod.no> References: <87sihkicso.fsf@Rainer.invalid> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1416668478 19131 80.91.229.3 (22 Nov 2014 15:01:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 22 Nov 2014 15:01:18 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 22 16:01:11 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 1XsCBS-0004R4-UH for ged-emacs-devel@m.gmane.org; Sat, 22 Nov 2014 16:01:11 +0100 Original-Received: from localhost ([::1]:45707 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XsCBS-0000jB-KF for ged-emacs-devel@m.gmane.org; Sat, 22 Nov 2014 10:01:10 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36225) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XsCB9-0000iL-QN for emacs-devel@gnu.org; Sat, 22 Nov 2014 10:00:58 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XsCB2-0005lm-8t for emacs-devel@gnu.org; Sat, 22 Nov 2014 10:00:51 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:42214) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XsCB2-0005lS-1d for emacs-devel@gnu.org; Sat, 22 Nov 2014 10:00:44 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XsCAz-0004Gp-EX for emacs-devel@gnu.org; Sat, 22 Nov 2014 16:00:41 +0100 Original-Received: from cm-84.208.248.210.getinternet.no ([84.208.248.210]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Nov 2014 16:00:41 +0100 Original-Received: from sb by cm-84.208.248.210.getinternet.no with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Nov 2014 16:00:41 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 31 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: cm-84.208.248.210.getinternet.no Mail-Copies-To: never User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.4 (gnu/linux) Cancel-Lock: sha1:KncoSw0MD2FLBC+PVtN15r2lyVk= 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:178011 Archived-At: >>>>> Lars Magne Ingebrigtsen : > A long, complicated git command isn't better than one simple git > command and then a "mv". I like to copy-paste ready-to-use commands from HOWTOs. And the fewer copy-pastes I have to do, the better: less work, less that can go wrong. The length, and complicated-ness of the copy-pasted command line doesn't really matter (as long as it works...). Note: I think the document is a great idea. I really like HOWTOs with canned commands that can be copy-pasted and will do the right thing, without me having to think too much. >> For the purposes of a robust list of copy-paste commands, using just >> what's in git itself is better than using a script that may, or may >> not, be present. > And is that command as good as what new-workdir does? My guess is that the git clone command would be better, ie. a 4-6 old contributed script vs. something that is standard functionality of git-clone. My understanding is that they currently pretty much will do the same thing (symlink the individual files of the .git directory of the original), but the git built-in functionality will move away from the reliance on symlinks i the future.