On Fri, 19 Jun 2015 21:08:00 +0200
Konrád Lőrinczi <klorin...@gmail.com> wrote:

> Thanks very much for your answer!
> It is really a deeply technical answer.
> Maybe are you one of developers of GIT?

Thanks!  No, I'm a mere enthusiast.

> As for bare repo it doesn't make possible to edit under Windows, then
> checkout under Debian.
> As for the git sparse checkout it is a good idea, but I'm afraid,
> that if I ignore iscsi/nodes path, then this will be OK for Windows,
> but on Debian, in case of a data loss & need of restore, these files
> will be not checked out and restored.

I don't really understand.
One only ever need to check files out if one intends to read them or
modify them (typicall to record another commit).  Well, if you only
need to read files you don't actually have to check them out -- it's
just convenient.

In other words, the work tree in a regular (non-bare) repository
files whose contents are *copies* of objects actually stored in the Git
repository.  To say it differently, the work tree is completely
redundant with regard to the repository.  That's why bare repos
(those used for collaboration) do not have any work tree attached to
them (so nothing is ever checked out of them) and yet they perfectly
store all the history pushed into them.

> Both are partially good solutions, but not fully perfect.

I'm afraid your problem is a red herring.
You only need to check those file out if you intend to *edit* them and
then create a new commit.  While I might fathom a reason for this,
it still appears that the repo produced by etckeeper is to be backed
up, not modified.  To do this, all you need is to just clone your
etckeeper repo to a *bare* repository once and then periodically fetch
new stuff there.

> Should I send the use case to the git developer list?

I dunno.  Let's figure out what's your actual use case first.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to