git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Composing git repositories

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 2, 2013, 19:09 UTC
Message-ID
<7vr4isda1u.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130402185426.GG28148@google.com>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 20 quoted lines
> ..., 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.

Previous: Jonathan NiederNext: Ramkumar Ramachandra
Message 35 of 43 in “Composing git repositories”
  1. Ramkumar RamachandraMar 26, 2013
  2. Junio C HamanoMar 26, 2013
  3. Ramkumar RamachandraMar 27, 2013
  4. Junio C HamanoMar 27, 2013
  5. Ramkumar RamachandraMar 27, 2013
  6. Junio C HamanoMar 27, 2013
  7. Jonathan NiederMar 27, 2013
  8. Junio C HamanoMar 27, 2013
  9. Jonathan NiederMar 27, 2013
  10. Ramkumar RamachandraMar 28, 2013
  11. Jens LehmannMar 28, 2013
  12. Ramkumar RamachandraMar 28, 2013
  13. Jonathan NiederMar 28, 2013
  14. Jens LehmannMar 28, 2013
  15. Jens LehmannMar 27, 2013
  16. Ramkumar RamachandraMar 28, 2013
  17. Jens LehmannMar 28, 2013
  18. Ramkumar RamachandraMar 31, 2013
  19. Jonathan NiederMar 31, 2013
  20. Ramkumar RamachandraApr 2, 2013
  21. Jeff KingApr 2, 2013
  22. Ramkumar RamachandraApr 2, 2013
  23. Jens LehmannApr 2, 2013
  24. Junio C HamanoApr 2, 2013
  25. Junio C HamanoApr 4, 2013
  26. Duy NguyenApr 5, 2013
  27. Junio C HamanoApr 5, 2013
  28. Duy NguyenApr 5, 2013
  29. Jens LehmannApr 5, 2013
  30. Phil HordMar 31, 2013
  31. Jens LehmannApr 1, 2013
  32. Phil HordApr 1, 2013
  33. Ramkumar RamachandraApr 2, 2013
  34. Jonathan NiederApr 2, 2013
  35. Junio C HamanoApr 2, 2013
  36. Ramkumar RamachandraApr 2, 2013
  37. Jonathan NiederApr 2, 2013
  38. Ramkumar RamachandraApr 2, 2013
  39. Ramkumar RamachandraApr 2, 2013
  40. Jens LehmannApr 2, 2013
  41. Jens LehmannApr 1, 2013
  42. Seth RobertsonApr 1, 2013
  43. Ramkumar RamachandraApr 2, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.