# Items not covered by repository-layout.txt

4 messages from 2006-07-10 to 2006-07-11. Participants: Jakub Narebski, Junio C Hamano.
Thread: https://gitlist.dev/t/4838

## Jakub Narebski, 2006-07-10 20:46

Subject: Items not covered by repository-layout.txt
Message-ID: <e8ue98$o7t$1@sea.gmane.org>
URL: https://gitlist.dev/e/e8ue98%24o7t%241%40sea.gmane.org

```
I have noticed few files in .git/ directory which currently are not covered
(and neither is their format) by Documentation/repository-layout.txt

* COMMIT_EDITMSG (temporary file, when I decided during writing commit
  message that I should change something before commit)
* FETCH_HEAD (format?)
* HEAD, ORIG_HEAD and probably some other *_HEAD
* .tmp-vtag (I'm not sure what have left that, probably git-verify-tag
  broken due to lack of signing PGP keys)
* description file

I know they are fairly obvious, but having everything that one could fing in
his/her git-core managed .git repository would be nice... 
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

```

## Junio C Hamano, 2006-07-10 21:29

Subject: Re: Items not covered by repository-layout.txt
Message-ID: <7v1wstb12x.fsf@assigned-by-dhcp.cox.net>
URL: https://gitlist.dev/e/7v1wstb12x.fsf%40assigned-by-dhcp.cox.net
In-Reply-To: <e8ue98$o7t$1@sea.gmane.org>

```
Jakub Narebski <jnareb@gmail.com> writes:

> I have noticed few files in .git/ directory which currently are not covered
> (and neither is their format) by Documentation/repository-layout.txt
>
> * COMMIT_EDITMSG (temporary file, when I decided during writing commit
>   message that I should change something before commit)
> * FETCH_HEAD (format?)
> * HEAD, ORIG_HEAD and probably some other *_HEAD
> * .tmp-vtag (I'm not sure what have left that, probably git-verify-tag
>   broken due to lack of signing PGP keys)
> * description file
>
> I know they are fairly obvious, but having everything that one could fing in
> his/her git-core managed .git repository would be nice... 

Yup, please make it so.

```

## Jakub Narebski, 2006-07-10 21:42

Subject: Re: Items not covered by repository-layout.txt
Message-ID: <e8uhjg$5o1$1@sea.gmane.org>
URL: https://gitlist.dev/e/e8uhjg%245o1%241%40sea.gmane.org
In-Reply-To: <7v1wstb12x.fsf@assigned-by-dhcp.cox.net>

```
Junio C Hamano wrote:

> Jakub Narebski <jnareb@gmail.com> writes:
> 
>> I have noticed few files in .git/ directory which currently are not covered
>> (and neither is their format) by Documentation/repository-layout.txt
>>
>> * COMMIT_EDITMSG (temporary file, when I decided during writing commit
>>   message that I should change something before commit)
>> * FETCH_HEAD (format?)
>> * HEAD, ORIG_HEAD and probably some other *_HEAD
>> * .tmp-vtag (I'm not sure what have left that, probably git-verify-tag
>>   broken due to lack of signing PGP keys)
>> * description file
>>
>> I know they are fairly obvious, but having everything that one could fing in
>> his/her git-core managed .git repository would be nice... 

I have just noticed that _config_ file (!)is not covered by repository-layout.txt
 
> Yup, please make it so.

Could you then tell me what is the format of FETCH_HEAD and what other *_HEADs 
can be seen in $GIT_DIR (MERGE_HEAD?)?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

```

## Junio C Hamano, 2006-07-11 00:23

Subject: Re: Items not covered by repository-layout.txt
Message-ID: <7vlkr16lc6.fsf@assigned-by-dhcp.cox.net>
URL: https://gitlist.dev/e/7vlkr16lc6.fsf%40assigned-by-dhcp.cox.net
In-Reply-To: <e8uhjg$5o1$1@sea.gmane.org>

```
Jakub Narebski <jnareb@gmail.com> writes:

> Could you then tell me what is the format of FETCH_HEAD and what other *_HEADs 
> can be seen in $GIT_DIR (MERGE_HEAD?)?

Which essentially is that you are telling me to do that, but I
am a bit busy this week.

If you can use the source to figure them out, that would be
great; otherwise this can wait or others can chime in.

For FETCH_HEAD fmt-merge-msg and git-pull would be helpful.
The general format is, one entry per line:

	object name <TAB> merge-marker <TAB> notes

where merge-marker is either empty (for commits to be merged by
git-pull that called git-fetch) or not-for-merge, and notes is a
human readable comment that describes where that object came
from.  Note that this is read both by humans _AND_ machine;
fmt-merge-msg relies on how it is stated.

Others "git grep -e _HEAD -- '*.sh'" perhaps.

	ORIG_HEAD - used to keep the value of HEAD before we do
                    anything we might regret

	MERGE_HEAD - one or more commit object names that are
                    being merged into the current branch during
                    a merge.

	MERGE_MSG - generated message for an automerge.

```