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

Applying patches in a directory that isn't a repository

From
Geoff Russell <geoffrey.russell@gmail.com>
Date
Jun 29, 2007, 06:07 UTC
Message-ID
<93c3eada0706282307i7a22bd27w6ca10839d36ea4eb@mail.gmail.com>
In-Reply-To
<93c3eada0706280153w1898be80u7785ef2b2b1dd188@mail.gmail.com>
Hi,
I'm trying to use git for software distribution.

The system is a directory of about 450mb comprising binaries, datafiles and scripts. The full repository is about 1.1gb. The users don't really need .git except when we login to pull upgrades for them. It would be nicer not to have the .git directory and just distribute patches which we would apply for our users.

But "git am" needs (AFAIK) a full repository. Is there a way to apply a patch without .git being present?

I can see the advantages of our users having the full repository, so maybe we should just distribute by DVD (currently we use CDs) and forget about it, but for download purposes, 450mb is nicer than 1.1gb.

Cheers, Geoff Russell

Next: Junio C Hamano
Message 1 of 9 in “Applying patches in a directory that isn't a repository”
  1. Geoff RussellJun 29, 2007
  2. Junio C HamanoJun 29, 2007
  3. 1/4 diffcore_count_changes: pass diffcore_filespecJunio C Hamano, Jun 29, 2007
  4. 2/4 diffcore_filespec: add is_binaryJunio C Hamano, Jun 29, 2007
  5. 3/4 diffcore-delta.c: update the comment on the algorithm.Junio C Hamano, Jun 29, 2007
  6. 4/4 diffcore-delta.c: Ignore CR in CRLF for text filesJunio C Hamano, Jun 29, 2007
  7. しらいしななこJun 29, 2007
  8. Junio C HamanoJun 29, 2007
  9. Geoff RussellJun 30, 2007

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.