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

Re: linux-next: unneeded merge in the security tree

From
Theodore Ts'o <tytso@mit.edu>
Date
Mar 12, 2013, 21:20 UTC
Message-ID
<20130312212027.GE14792@thunk.org>
In-Reply-To
<CA+55aFzFLDcN-1GKae6Xqrns59K1xOD_HPzuv2Lv1__fZpqFMw@mail.gmail.com>
What if we added the ability to do something like this:
[remote "origin"]
	url = git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
	fetch = +refs/heads/master:refs/heads/master
	mergeoptions = --ff-only

This would be an analog to branch.<name>.mergeoptions, but it would apply to the source of the pull request, instead of the destination.

That way, people who do a "git pull" from Linus's tree would get the protection of --ff-only, while pulls from submaintainer trees would automatically get a merge commit, which is what we want.

It doesn't handle the case of a submaintainer pulling from a maintainer in a back-merge scenario, but that should be a pretty rare case, so maybe that's OK.

      	     	       	   	- Ted
Previous: Junio C HamanoNext: Linus Torvalds
Message 5 of 12 in “Re: linux-next: unneeded merge in the security tree”
  1. Linus TorvaldsMar 12, 2013
  2. Geert UytterhoevenMar 12, 2013
  3. Junio C HamanoMar 12, 2013
  4. Junio C HamanoMar 12, 2013
  5. Theodore Ts'oMar 12, 2013
  6. Linus TorvaldsMar 12, 2013
  7. Junio C HamanoMar 12, 2013
  8. Linus TorvaldsMar 12, 2013
  9. Junio C HamanoMar 12, 2013
  10. Junio C HamanoMar 12, 2013
  11. Theodore Ts'oMar 13, 2013
  12. Junio C HamanoMar 13, 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.