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

[RFC] git email submissions

From
JGJeff Garzik <jgarzik@pobox.com>
Date
Nov 16, 2005, 14:38 UTC
Message-ID
<437B4472.1080401@pobox.com>

For people without _any_ hosting, it would be nice to give them a method to submit some git changes via email.

It seems like most of the necessary stuff is already present in git to bundle up a set of changes. The open questions in my mind are

- what form would the emails take?  MIME-attach a .pack file, plus a 
GPG-signed sha1sum in a separate attachment?
- what's the easiest user interface for selecting the changes?  for my 
usage, it would be
	GIT_GPG_AUTHOR=jgarzik... \
	GIT_DEF_HEADERS=./email.headers \
	git-mkmail --sign master..upstream > email.rfc822
	Enter GPG passphrase:
- what user interface does a kernel maintainer use, to merge changes 
submitted using this method?
- is this all pointless, since the submittor could just email patches? 
[IMO no, git trees are better merges than emailed patches]

Overall, I was thinking it would be nice to have some way to safely transmit a small part of a git tree, including all history information, since its easier to merge git trees than patches.

And for someone without the resources to obtain hosting, email may be the only way to publish a git sub-tree.

	Jeff
Next: Petr Baudis
Message 1 of 9 in “[RFC] git email submissions”
  1. Jeff GarzikNov 16, 2005
  2. Petr BaudisNov 16, 2005
  3. Linus TorvaldsNov 16, 2005
  4. H. Peter AnvinNov 16, 2005
  5. Jeff GarzikNov 16, 2005
  6. Matthias UrlichsNov 16, 2005
  7. Junio C HamanoNov 19, 2005
  8. Martin LanghoffNov 17, 2005
  9. H. Peter AnvinNov 17, 2005

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.