From: Steinar Bang <sb@dod.no>
To: emacs-devel@gnu.org
Subject: Re: A simple git workflow for the rest of us
Date: Sat, 22 Nov 2014 16:00:30 +0100 [thread overview]
Message-ID: <87ioi72sc1.fsf@dod.no> (raw)
In-Reply-To: m3389b4auh.fsf@stories.gnus.org
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> 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.
next prev parent reply other threads:[~2014-11-22 15:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 16:09 A simple git workflow for the rest of us Lars Magne Ingebrigtsen
2014-11-15 16:38 ` Eli Zaretskii
2014-11-15 17:08 ` Lars Magne Ingebrigtsen
2014-11-16 2:57 ` Ted Zlatanov
2014-11-15 17:43 ` Achim Gratz
2014-11-15 18:04 ` Eli Zaretskii
2014-11-15 17:39 ` Achim Gratz
2014-11-15 17:47 ` Lars Magne Ingebrigtsen
2014-11-15 19:47 ` Karl Fogel
2014-11-16 19:05 ` Bill Wohler
2014-11-22 9:23 ` Steinar Bang
2014-11-22 13:35 ` Lars Magne Ingebrigtsen
2014-11-22 15:00 ` Steinar Bang [this message]
2014-11-22 15:26 ` Lars Magne Ingebrigtsen
2014-11-15 18:17 ` Andreas Schwab
2014-11-15 20:20 ` Kelvin White
2014-11-15 20:54 ` Kelvin White
2014-11-16 19:33 ` Bill Wohler
2014-11-16 19:43 ` Lars Magne Ingebrigtsen
2014-11-16 20:12 ` Ted Zlatanov
2014-11-16 20:19 ` Eli Zaretskii
2014-11-22 9:29 ` Steinar Bang
2014-11-23 18:28 ` Bill Wohler
2014-11-24 15:25 ` Sergey Organov
2014-11-15 19:08 ` Lars Magne Ingebrigtsen
2014-11-15 19:46 ` Andreas Schwab
2014-11-16 14:13 ` Lars Magne Ingebrigtsen
2014-11-16 14:34 ` David Engster
2014-11-16 14:42 ` Lars Magne Ingebrigtsen
2014-11-16 14:50 ` David Engster
2014-11-16 14:54 ` Lars Magne Ingebrigtsen
2014-11-16 15:19 ` David Kastrup
2014-11-16 14:36 ` Achim Gratz
2014-11-16 2:15 ` Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ioi72sc1.fsf@dod.no \
--to=sb@dod.no \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.