On Thu, 1 Sep 2011 08:15:58 -0700 (PDT) Thomas Ferris Nicolaisen <[email protected]> wrote:
[...] > I have no idea what the effect of adding devices, blocks or channels, > but symbolic links are just stored as you would expect. [...] > I have no idea why you would want to do any of this though. I would > generally regard having these special files inside your source code > as a bad idea. I think you're concentrating too much on that "source code" idea. If we instead look at these two things: a) Unix has special files (such as devices, named pipes etc), b) Git tracks hierarchies of files, then one can think of using Git as something like a "versioned tar". For instance, one could create a Git repo from a baseline (reference) hierarchy of files (even the whole contents under "/") and then replicate it to other hosts by cloning. Or use this scheme as a replacement for rdiff-backup or the like. Not that I think it's a bright idea but still... Also a way more simpler use case can be thought of: one might want to have, say, a set of named pipes in their repo to use them for testing. Though in this particular case I'd reliy on their dynamic creation/deletion by the test suite itself. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
