Re: Composing git repositories

Jonathan Nieder [off-list ref] writes:

..., but it might make sense to start respecting a .motd file to allow
the following in a hypothetical world where everyone who clones git
uses the same scripts Junio does:

	$ git clone git://repo.or.cz/git.git
	Cloning into 'git'...
	remote: Counting objects: 151283, done.
	remote: Compressing objects: 100% (38546/38546), done.
	remote: Total 151283 (delta 111004), reused 151073 (delta 110797)
	Receiving objects: 100% (151283/151283), 36.39 MiB | 7.66 MiB/s, done.
	Resolving deltas: 100% (111004/111004), done.

	Don't forget to "git clone -b todo git://repo.or.cz/git.git git/Meta"
	for maintenance scripts.
	$

That would allow you to include an arbitrary setup script (including
cloning dependencies as well as running "autoreconf" or whatever) and
give people cloning a quick reminder to inspect it if paranoid and
then run it.

I do not think motd is a good fit for the above; the message will
disappear any time once you are done cloning.  Depending on how
common the use of Meta/ should be, it is more appropriate to have
such an instruction in README or some other places as tracked
contents.

I do not know if the above is related to the problem Ram is trying
to solve or a totally orthogonal issue, though.