{"thread":{"id":"509","subject":"[PATCH 0/5] git-tar-tree: add symlink support","startedAt":"2005-05-06T20:55:29Z","lastAt":"2005-05-06T20:55:29Z","messageCount":1,"participants":["Rene Scharfe"],"isPatch":true,"patchVersion":1,"patchTotal":5},"messages":[{"id":"2702","messageId":"20050506205529.GA19518@lsrfire.ath.cx","threadId":"509","inReplyTo":null,"subject":"[PATCH 0/5] git-tar-tree: add symlink support","fromName":"Rene Scharfe","fromEmail":"rene.scharfe@lsrfire.ath.cx","sentAt":"2005-05-06T20:55:29Z","receivedAt":"2005-05-06T20:55:29Z","isPatch":true,"sender":{"key":"l.s.r@web.de","avatar":"https://avatars.githubusercontent.com/u/26122331?v=4"},"body":"Since symlinks can be stored inside GIT, git-tar-tree should properly\nhandle them, too.  The first three patches do a bit of cleanup to make\nadding symlink support easier.  The fourth patch actually dirties the\ncode, also to make the fifth one easier. :)  I just couldn't think of a\nbetter way to split the changes and a combined patch of 4&5 did too much\nat once.\n\nIf a link target is longer than 100 chars than an extended header is\ncreated.  Because of the way git-tar-tree handles extended headers that\nmeans the sum of path and target of a symlink must be less than about\n490 chars.  This is not a limitation of the archive format, so we can\nfix it later.\n\nRene\n"}]}