{"thread":{"id":"5407","subject":"File archiver using git","startedAt":"2006-08-27T13:10:34Z","lastAt":"2006-08-28T00:40:20Z","messageCount":4,"participants":["Matt McCutchen","Grzegorz Kulewski","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"25984","messageId":"3bbc18d20608270610o102968d2kd340d40843262dc5@mail.gmail.com","threadId":"5407","inReplyTo":null,"subject":"File archiver using git","fromName":"Matt McCutchen","fromEmail":"hashproduct@gmail.com","sentAt":"2006-08-27T13:10:34Z","receivedAt":"2006-08-27T13:10:34Z","isPatch":false,"sender":{"key":"matt@mattmccutchen.net","avatar":"https://avatars.githubusercontent.com/u/8885753?v=4"},"body":"Dear git people,\n\nYou might like the two attached scripts that I wrote around git to\npack file trees containing lots of redundancy into very small\npackages.  For example, if I have ten slightly different versions of a\npiece of software because I didn't use version control, I can use\ngitar to compress them together.\n\nMatt\n"},{"id":"25985","messageId":"Pine.LNX.4.63.0608271528130.8018@alpha.polcom.net","threadId":"5407","inReplyTo":"3bbc18d20608270610o102968d2kd340d40843262dc5@mail.gmail.com","subject":"Re: File archiver using git","fromName":"Grzegorz Kulewski","fromEmail":"kangur@polcom.net","sentAt":"2006-08-27T13:31:30Z","receivedAt":"2006-08-27T13:31:30Z","isPatch":false,"sender":{"key":"kangur@polcom.net","avatar":null},"body":"On Sun, 27 Aug 2006, Matt McCutchen wrote:\n> Dear git people,\n>\n> You might like the two attached scripts that I wrote around git to\n> pack file trees containing lots of redundancy into very small\n> packages.  For example, if I have ten slightly different versions of a\n> piece of software because I didn't use version control, I can use\n> gitar to compress them together.\n\nDoes it (and GIT in general) work ok with file permisions, ownership, soft \nand hard links, named sockets, device files and similar \"strange\" \nfilesystem objects? Do I need any options to GIT to make it work with \nthem?\n\nCan I for example securely backup or even version-control /etc directory?\n\n\nGrzegorz Kulewski\n"},{"id":"25989","messageId":"ecse17$2q3$1@sea.gmane.org","threadId":"5407","inReplyTo":"Pine.LNX.4.63.0608271528130.8018@alpha.polcom.net","subject":"Re: File archiver using git","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-08-27T15:34:04Z","receivedAt":"2006-08-27T15:34:04Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Grzegorz Kulewski wrote:\n\n> On Sun, 27 Aug 2006, Matt McCutchen wrote:\n>> Dear git people,\n>>\n>> You might like the two attached scripts that I wrote around git to\n>> pack file trees containing lots of redundancy into very small\n>> packages.  For example, if I have ten slightly different versions of a\n>> piece of software because I didn't use version control, I can use\n>> gitar to compress them together.\n> \n> Does it (and GIT in general) work ok with file permisions, ownership, soft \n> and hard links, named sockets, device files and similar \"strange\" \n> filesystem objects? Do I need any options to GIT to make it work with \n> them?\n\nGit in general only preserves executable bit, deals with symlinks,\nhardlinks after a fashion (stored once, but unpacked/checked out as separate\nfiles, not hardlinked), and does not deal with other \"strange\" filesystem\nobjects as far as I know.\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"},{"id":"26021","messageId":"3bbc18d20608271740m63be7ae9qc49ec944f5131030@mail.gmail.com","threadId":"5407","inReplyTo":"Pine.LNX.4.63.0608271528130.8018@alpha.polcom.net","subject":"Re: File archiver using git","fromName":"Matt McCutchen","fromEmail":"hashproduct@gmail.com","sentAt":"2006-08-28T00:40:20Z","receivedAt":"2006-08-28T00:40:20Z","isPatch":false,"sender":{"key":"matt@mattmccutchen.net","avatar":"https://avatars.githubusercontent.com/u/8885753?v=4"},"body":"On 8/27/06, Grzegorz Kulewski <kangur@polcom.net> wrote:\n> Does it (and GIT in general) work ok with file permisions, ownership, soft\n> and hard links, named sockets, device files and similar \"strange\"\n> filesystem objects? Do I need any options to GIT to make it work with\n> them?\n\nGit tracks data, not filesystems.  That means it doesn't handle any of\nthe things you mentioned except soft links.  It doesn't even handle\nempty directories, though I don't accept the argument that they do not\nconstitute data.  If you want to capture a filesystem, I would\nrecommend running \"find . -ls\" to create a listing file from which\neverything you mentioned can be reconstructed and then putting the\nfilesystem together with the listing file into git.\n\n> Can I for example securely backup or even version-control /etc directory?\n\nWith the above technique, you can do both.  However, if you just want\nto back up /etc, you might be better served by a backup tool.  For\nexample, I use rsnapshot ( http://www.rsnapshot.org/ ).\n\nMatt\n"}]}