From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: Re: Multiple checkout copies
Date: Tue, 03 Feb 2015 20:25:26 +0000 [thread overview]
Message-ID: <87386mhhe1.fsf@violet.siamics.net> (raw)
In-Reply-To: <87vbji236v.fsf@fencepost.gnu.org> (David Kastrup's message of "Tue, 03 Feb 2015 20:41:12 +0100")
>>>>> David Kastrup <dak@gnu.org> writes:
>>>>> Ivan Shmakov <ivan@siamics.net> writes:
>>>>> David Kastrup <dak@gnu.org> writes:
>>> "I'm typically interested in" is no base for promoting problematic
>>> workflows since it violates the "do not use it unless you
>>> understand what it does" dictum for the recipient of such a recipe.
>> The whole idea behind this discussion is to clarify when --shared is
>> reasonable, — and when it isn’t. Isn’t it?
> And the manual page clearly states that it requires to know what you
> are doing. That makes it feasible for use in a script, and
> unfeasible for use in a recipe: the latter _can_ and will be varied,
> violating the "do not use it unless you understand what it does"
> prerequisite given in its manual page.
> And all of the handwaving and qualifications _after_ having the
> problems pointed out make _very_ obvious that the required
> information for using it safely is not likely to be communicated in
> informal discussions.
I’m getting an impression that the above should make me feeling
guilt or ashamed of sharing my workflow with the audience.
But I still do not, nor see the reason to.
> In addition, we've had --shared confused with --local (which is
> implied anyway).
FTR, in my initial message, I’ve indeed confused --shared with
--local as the /default/ for git-clone(1), and even corrected
myself [1]. I didn’t confuse the /effects/ of these options.
> So the takeaway is not to use any options in connection with creating
> local clones manually.
I disagree.
> That steers around all of the not reliably reproducible problems, at
> a mostly moderate cost in disk usage.
> "Handling a foot gun is not hard and can be fun" is a frequent
> software engineering pain vector.
In this discussion, I saw no scenario under which my approach,
as given in [1], would fail (but surely would appreciate any.)
It wasn’t my intent to make claims regarding the use of --shared
outside of that particular approach.
[1] news:87oapcgp2c.fsf@violet.siamics.net
http://permalink.gmane.org/gmane.emacs.devel/182278
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2015-02-03 20:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 20:34 Multiple checkout copies Richard Stallman
2015-02-01 21:43 ` Paul Eggert
2015-02-02 13:35 ` Richard Stallman
2015-02-02 15:19 ` Elias Mårtenson
2015-02-03 1:10 ` Richard Stallman
2015-02-03 1:32 ` Paul Eggert
2015-02-03 8:40 ` David Kastrup
2015-02-02 17:42 ` Ivan Shmakov
2015-02-02 18:12 ` Ivan Shmakov
2015-02-03 1:10 ` Richard Stallman
2015-02-03 7:14 ` Ivan Shmakov
2015-02-03 10:02 ` Achim Gratz
2015-02-03 10:22 ` David Kastrup
2015-02-03 12:53 ` Achim Gratz
2015-02-03 13:15 ` David Kastrup
2015-02-03 13:37 ` Ivan Shmakov
2015-02-03 13:57 ` David Kastrup
2015-02-03 18:30 ` Ivan Shmakov
2015-02-03 18:53 ` David Kastrup
2015-02-03 19:17 ` Ivan Shmakov
2015-02-03 19:41 ` David Kastrup
2015-02-03 20:25 ` Ivan Shmakov [this message]
2015-02-04 23:02 ` Richard Stallman
2015-02-03 17:46 ` Stefan Monnier
2015-02-03 16:50 ` Steinar Bang
2015-02-03 17:05 ` David Kastrup
2015-02-03 22:55 ` Steinar Bang
2015-02-03 23:05 ` Richard Stallman
2015-02-04 8:48 ` Achim Gratz
2015-02-04 8:55 ` David Kastrup
2015-02-04 12:02 ` Ivan Shmakov
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=87386mhhe1.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--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.