{"thread":{"id":"4838","subject":"Items not covered by repository-layout.txt","startedAt":"2006-07-10T20:46:02Z","lastAt":"2006-07-11T00:23:21Z","messageCount":4,"participants":["Jakub Narebski","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"23580","messageId":"e8ue98$o7t$1@sea.gmane.org","threadId":"4838","inReplyTo":null,"subject":"Items not covered by repository-layout.txt","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-07-10T20:46:02Z","receivedAt":"2006-07-10T20:46:02Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"I have noticed few files in .git/ directory which currently are not covered\n(and neither is their format) by Documentation/repository-layout.txt\n\n* COMMIT_EDITMSG (temporary file, when I decided during writing commit\n message that I should change something before commit)\n* FETCH_HEAD (format?)\n* HEAD, ORIG_HEAD and probably some other *_HEAD\n* .tmp-vtag (I'm not sure what have left that, probably git-verify-tag\n broken due to lack of signing PGP keys)\n* description file\n\nI know they are fairly obvious, but having everything that one could fing in\nhis/her git-core managed .git repository would be nice... \n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"},{"id":"23583","messageId":"7v1wstb12x.fsf@assigned-by-dhcp.cox.net","threadId":"4838","inReplyTo":"e8ue98$o7t$1@sea.gmane.org","subject":"Re: Items not covered by repository-layout.txt","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-07-10T21:29:42Z","receivedAt":"2006-07-10T21:29:42Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jakub Narebski writes:\n\n> I have noticed few files in .git/ directory which currently are not covered\n> (and neither is their format) by Documentation/repository-layout.txt\n>\n> * COMMIT_EDITMSG (temporary file, when I decided during writing commit\n> message that I should change something before commit)\n> * FETCH_HEAD (format?)\n> * HEAD, ORIG_HEAD and probably some other *_HEAD\n> * .tmp-vtag (I'm not sure what have left that, probably git-verify-tag\n> broken due to lack of signing PGP keys)\n> * description file\n>\n> I know they are fairly obvious, but having everything that one could fing in\n> his/her git-core managed .git repository would be nice... \n\nYup, please make it so.\n"},{"id":"23585","messageId":"e8uhjg$5o1$1@sea.gmane.org","threadId":"4838","inReplyTo":"7v1wstb12x.fsf@assigned-by-dhcp.cox.net","subject":"Re: Items not covered by repository-layout.txt","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-07-10T21:42:42Z","receivedAt":"2006-07-10T21:42:42Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Junio C Hamano wrote:\n\n> Jakub Narebski writes:\n> \n>> I have noticed few files in .git/ directory which currently are not covered\n>> (and neither is their format) by Documentation/repository-layout.txt\n>>\n>> * COMMIT_EDITMSG (temporary file, when I decided during writing commit\n>> message that I should change something before commit)\n>> * FETCH_HEAD (format?)\n>> * HEAD, ORIG_HEAD and probably some other *_HEAD\n>> * .tmp-vtag (I'm not sure what have left that, probably git-verify-tag\n>> broken due to lack of signing PGP keys)\n>> * description file\n>>\n>> I know they are fairly obvious, but having everything that one could fing in\n>> his/her git-core managed .git repository would be nice... \n\nI have just noticed that _config_ file (!)is not covered by repository-layout.txt\n \n> Yup, please make it so.\n\nCould you then tell me what is the format of FETCH_HEAD and what other *_HEADs \ncan be seen in $GIT_DIR (MERGE_HEAD?)?\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"},{"id":"23601","messageId":"7vlkr16lc6.fsf@assigned-by-dhcp.cox.net","threadId":"4838","inReplyTo":"e8uhjg$5o1$1@sea.gmane.org","subject":"Re: Items not covered by repository-layout.txt","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-07-11T00:23:21Z","receivedAt":"2006-07-11T00:23:21Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jakub Narebski writes:\n\n> Could you then tell me what is the format of FETCH_HEAD and what other *_HEADs \n> can be seen in $GIT_DIR (MERGE_HEAD?)?\n\nWhich essentially is that you are telling me to do that, but I\nam a bit busy this week.\n\nIf you can use the source to figure them out, that would be\ngreat; otherwise this can wait or others can chime in.\n\nFor FETCH_HEAD fmt-merge-msg and git-pull would be helpful.\nThe general format is, one entry per line:\n\n\tobject name merge-marker notes\n\nwhere merge-marker is either empty (for commits to be merged by\ngit-pull that called git-fetch) or not-for-merge, and notes is a\nhuman readable comment that describes where that object came\nfrom. Note that this is read both by humans _AND_ machine;\nfmt-merge-msg relies on how it is stated.\n\nOthers \"git grep -e _HEAD -- '*.sh'\" perhaps.\n\n\tORIG_HEAD - used to keep the value of HEAD before we do\n anything we might regret\n\n\tMERGE_HEAD - one or more commit object names that are\n being merged into the current branch during\n a merge.\n\n\tMERGE_MSG - generated message for an automerge.\n"}]}