git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Arkadij Chistyj <arkdchst@gmail.com>
Cc: git@vger.kernel.org, "brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: Question - .git subdirectories
Date: Thu, 31 Oct 2019 16:01:06 -0700	[thread overview]
Message-ID: <20191031230106.GB211076@google.com> (raw)
In-Reply-To: <CABf25VhaqrbtRTpL5ZNRy59o4JSsiKpF3pk3+54sDCkvzdgAmw@mail.gmail.com>

Hi Arkadij,

Arkadij Chistyj wrote:
>                                               I just want that git
> treats my .git/ subdirs as plain dirs with any other names.
[...]
> It's very simple functionality but I can't find any simple and right solution.
> I just want to know is this possible or not? If not possible, then why?

To add to what brian wrote:

This is one of many things that Git doesn't track:

- empty directories
- full permissions for files it's tracking
- owner, group, other attributes
- resource fork on filesystems that support multiple forks

Git was initially designed to handle source code.  Later, people have
started to use it for tracking other kinds of documents, which has been
nice.  In general, when push comes to shove, the project has prioritized
making it work well for tracking source code and other documents.

Sometimes people find other uses for Git (deployment tool! home
directory tracker! configuration management system!).  It can be
fun[1]. :)  Ultimately, though, it's useful to keep the main goals of
Git in mind.

Sometimes people want to track a Git repository in another repository
as a source of test data for tests they include with their code.  For
this use, using a "git fast-export" stream or other method for
generating a repository at test time can work better, or, if one
really must use a repo-in-repo, using a bare repository.  Brian did a
good job of describing why.

Thanks and hope that helps,
Jonathan

[1] https://public-inbox.org/git/?q=ugfwiini

  parent reply	other threads:[~2019-10-31 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 12:26 Question - .git subdirectories Arkadij Chistyj
2019-10-31 20:20 ` brian m. carlson
2019-10-31 23:01 ` Jonathan Nieder [this message]
2019-11-02 19:14   ` Arkadij Chistyj

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=20191031230106.GB211076@google.com \
    --to=jrnieder@gmail.com \
    --cc=arkdchst@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    /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).