* git, isolation
@ 2017-11-03 16:33 Péter
2017-11-03 16:52 ` Dennis Kaarsemaker
0 siblings, 1 reply; 4+ messages in thread
From: Péter @ 2017-11-03 16:33 UTC (permalink / raw)
To: git
Hi,
If I do a "git commit", issue git operations, and at the end, issue a "rm <the_git_dir>", is there any guarantee that my
filesystem will be "clean", i.e. not polluted or otherwise modified by some git command? Are the git operations
restricted to the repo-directory (and possibly remote places, over network)? Do the git-directory behaves as it were
chroot-ed or be a sandbox? (Yet another words: is the git-directory isolated from the rest of the local filesystem (and
packaging system)?)
Péter
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git, isolation
2017-11-03 16:33 git, isolation Péter
@ 2017-11-03 16:52 ` Dennis Kaarsemaker
2017-11-03 17:18 ` Stefan Beller
0 siblings, 1 reply; 4+ messages in thread
From: Dennis Kaarsemaker @ 2017-11-03 16:52 UTC (permalink / raw)
To: Péter, git
On Fri, 2017-11-03 at 17:33 +0100, Péter wrote:
> Hi,
>
> If I do a "git commit", issue git operations, and at the end, issue a "rm <the_git_dir>", is there any guarantee that my
> filesystem will be "clean",
No.
> i.e. not polluted or otherwise modified by some git command? Are the git operations
> restricted to the repo-directory (and possibly remote places, over network)?
No.
> Do the git-directory behaves as it were
> chroot-ed or be a sandbox? (Yet another words: is the git-directory isolated from the rest of the local filesystem (and
> packaging system)?)
And no :)
Most git commands will not touch anything outside the main worktree and
the .git directory in there, but commands like 'git worktree' can be
used to create worktrees anywhere in the filesystem, and when you play
tricks with the GIT_WORK_TREE environment variable, you can do other
nasty things.
D.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git, isolation
2017-11-03 16:52 ` Dennis Kaarsemaker
@ 2017-11-03 17:18 ` Stefan Beller
0 siblings, 0 replies; 4+ messages in thread
From: Stefan Beller @ 2017-11-03 17:18 UTC (permalink / raw)
To: Dennis Kaarsemaker; +Cc: Péter, git
On Fri, Nov 3, 2017 at 9:52 AM, Dennis Kaarsemaker
<dennis@kaarsemaker.net> wrote:
> On Fri, 2017-11-03 at 17:33 +0100, Péter wrote:
>> Hi,
>>
>> If I do a "git commit", issue git operations, and at the end, issue a "rm <the_git_dir>", is there any guarantee that my
>> filesystem will be "clean",
>
> No.
>
>> i.e. not polluted or otherwise modified by some git command? Are the git operations
>> restricted to the repo-directory (and possibly remote places, over network)?
>
> No.
>
>> Do the git-directory behaves as it were
>> chroot-ed or be a sandbox? (Yet another words: is the git-directory isolated from the rest of the local filesystem (and
>> packaging system)?)
>
> And no :)
>
> Most git commands will not touch anything outside the main worktree and
> the .git directory in there, but commands like 'git worktree' can be
> used to create worktrees anywhere in the filesystem, and when you play
> tricks with the GIT_WORK_TREE environment variable, you can do other
> nasty things.
Or a more common thing, implemented earlier in Gits career:
git config --global ....
^ permalink raw reply [flat|nested] 4+ messages in thread
* git, isolation
@ 2017-11-03 16:36 Péter
0 siblings, 0 replies; 4+ messages in thread
From: Péter @ 2017-11-03 16:36 UTC (permalink / raw)
To: git
>If I do a "git commit"
"git clone"
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-11-03 17:18 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-11-03 16:33 git, isolation Péter
2017-11-03 16:52 ` Dennis Kaarsemaker
2017-11-03 17:18 ` Stefan Beller
-- strict thread matches above, loose matches on Subject: below --
2017-11-03 16:36 Péter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).