{"thread":{"id":"7414","subject":"tar commit header names","startedAt":"2007-03-26T16:39:30Z","lastAt":"2007-03-29T16:55:30Z","messageCount":3,"participants":["Daniel Barkalow","René Scharfe"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"38036","messageId":"Pine.LNX.4.64.0703261230420.6485@iabervon.org","threadId":"7414","inReplyTo":null,"subject":"tar commit header names","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2007-03-26T16:39:30Z","receivedAt":"2007-03-26T16:39:30Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"I'm entirely ignorant of pax header stuff, but would it be possible to \nhave the pax header specify which project this commit is from (which has \nto come from a git-archive option, clearly). Also, could \ngit-get-tar-commit-id have an option to look for more pax headers beyond \nthe first? (I'm building tar files by appending multiple archives for \ndifferent projects from git-archive, and I suddenly find the embedded \ncommit id is helpful, and surprisingly inaccessible in this context.)\n\n\t-Daniel\n*This .sig left intentionally blank*\n"},{"id":"38334","messageId":"460BE44B.8090301@lsrfire.ath.cx","threadId":"7414","inReplyTo":"Pine.LNX.4.64.0703261230420.6485@iabervon.org","subject":"Re: tar commit header names","fromName":"René Scharfe","fromEmail":"rene.scharfe@lsrfire.ath.cx","sentAt":"2007-03-29T16:07:39Z","receivedAt":"2007-03-29T16:07:39Z","isPatch":false,"sender":{"key":"l.s.r@web.de","avatar":"https://avatars.githubusercontent.com/u/26122331?v=4"},"body":"Daniel Barkalow schrieb:\n> I'm entirely ignorant of pax header stuff, but would it be possible to \n> have the pax header specify which project this commit is from (which has \n> to come from a git-archive option, clearly).\n\nTechnically, yes.  The commit ID is stored in a comment, more info could\nappended to it.  Adding more stuff there would necessitate an ordering\nscheme, though.  I'm not sure this is useful enough.  There already is a\nnice convention on where to store the project name, description and URL:\nin a file named 'README'. :)\n\n> Also, could \n> git-get-tar-commit-id have an option to look for more pax headers beyond \n> the first? (I'm building tar files by appending multiple archives for \n> different projects from git-archive, and I suddenly find the embedded \n> commit id is helpful, and surprisingly inaccessible in this context.)\n\nThis could be done, at the cost of git-get-tar-commit-id having to be\nable to really parse tar files in order to seek to the end of the first\nand thus to the start of the appended one.  Right now it simply reads\nthe first few bytes, quickly checks if this looks like a tar file and\nprints the commit ID, if one is found.\n\nThe right place to add generic archive comment extraction capabilities\n(with multi-archive support) would be a general purpose archiver like\nGNU tar, no?\n\nRené\n"},{"id":"38335","messageId":"Pine.LNX.4.64.0703291234090.6485@iabervon.org","threadId":"7414","inReplyTo":"460BE44B.8090301@lsrfire.ath.cx","subject":"Re: tar commit header names","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2007-03-29T16:55:30Z","receivedAt":"2007-03-29T16:55:30Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Thu, 29 Mar 2007, René Scharfe wrote:\n\n> Daniel Barkalow schrieb:\n> > I'm entirely ignorant of pax header stuff, but would it be possible to \n> > have the pax header specify which project this commit is from (which has \n> > to come from a git-archive option, clearly).\n> \n> Technically, yes.  The commit ID is stored in a comment, more info could\n> appended to it.  Adding more stuff there would necessitate an ordering\n> scheme, though.  I'm not sure this is useful enough.  There already is a\n> nice convention on where to store the project name, description and URL:\n> in a file named 'README'. :)\n\nAh, and the comment applies until the next comment, so the common prefix \nof the files in the area with the comment explains it. I was missing what \nthe rules for regions of applicability of pax global headers are. Now, if \nI could convince... something... to report what comments apply to what \nfiles, I'd be set. And that's clearly beyond the scope of git. (Although \nmaybe git-get-... should know how to invoke some other utility on a \nmultiple-project archive once some such tool is known.)\n\n\t-Daniel\n*This .sig left intentionally blank*"}]}