On Sat, 20 Jun 2015 10:07:17 +0200
Konrád Lőrinczi <klorin...@gmail.com> wrote:
> > > 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.
> If there would be no iscsi drive used on production server and no
> Windows machine used as work machine, then the whole solution would
> be working fine.
The way you check out files on your Windows box has nothing to do with
the contents of the repository you check these files out from (well,
you will be unable to edit those files but then again they are just
device nodes and hence have no content).
So I'd say using sparse checkout on Windows is a way to go in this
On a side note, it's interesting how device nodes ended up being
tracked by etckeeper. I'm not familiar with this tool, so my question
is: does it store ownership and access information of files it track?
Do the same apply to major/minor numbers of device node files?
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
For more options, visit https://groups.google.com/d/optout.