git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Beller <sbeller@google.com>
To: Dennis Kaarsemaker <dennis@kaarsemaker.net>
Cc: Péter <e2qb2a44f@prolan-power.hu>, git <git@vger.kernel.org>
Subject: Re: git, isolation
Date: Fri, 3 Nov 2017 10:18:49 -0700	[thread overview]
Message-ID: <CAGZ79kar+YbMyMK-ktOT3WZW5fZB89HL1QabsZAhofcGuSJSbg@mail.gmail.com> (raw)
In-Reply-To: <1509727946.1734.2.camel@kaarsemaker.net>

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 ....

  reply	other threads:[~2017-11-03 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 16:33 git, isolation Péter
2017-11-03 16:52 ` Dennis Kaarsemaker
2017-11-03 17:18   ` Stefan Beller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-03 16:36 Péter

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=CAGZ79kar+YbMyMK-ktOT3WZW5fZB89HL1QabsZAhofcGuSJSbg@mail.gmail.com \
    --to=sbeller@google.com \
    --cc=dennis@kaarsemaker.net \
    --cc=e2qb2a44f@prolan-power.hu \
    --cc=git@vger.kernel.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.
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).