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

Re: [RFC+PATCH 1/1] Move SCM interoperability tools into scm/

From
Petr Baudis <pasky@suse.cz>
Date
Jul 9, 2006, 22:13 UTC
Message-ID
<20060709221326.GU29115@pasky.or.cz>
In-Reply-To
<46a038f90607091426u5a6ea328h2090a876e51725ce@mail.gmail.com>

Dear diary, on Sun, Jul 09, 2006 at 11:26:59PM CEST, I got a letter where Martin Langhoff <martin.langhoff@gmail.com> said that...

> So I have to ask... what are the expected benefits of the move?

I've been meaning to do something like this for some time already; my itch have been the builtins. The tree size _is_ getting out of hand and a little more categorization of the sources would certainly help. Although I'd take a different approach:

	libgit/
	builtin/
	standalone/
	scripts/
> In any case, use /interop instead. /scm in the tree of an SCM could be
> anything ;-)
I agree on this point.
-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam
Previous: Martin LanghoffNext: Johannes Schindelin
Message 4 of 11 in “Move SCM interoperability tools into scm/”
  1. 1/1 Move SCM interoperability tools into scm/Ryan Anderson, Jul 9, 2006
  2. Johannes SchindelinJul 9, 2006
  3. Martin LanghoffJul 9, 2006
  4. Petr BaudisJul 9, 2006
  5. Johannes SchindelinJul 9, 2006
  6. Ryan AndersonJul 9, 2006
  7. Junio C HamanoJul 10, 2006
  8. Ryan AndersonJul 10, 2006
  9. Timo HirvonenJul 9, 2006
  10. Ryan AndersonJul 10, 2006
  11. Timo HirvonenJul 10, 2006

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.