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

Re: [PATCH] Implement git-quiltimport

From
Junio C Hamano <junkio@cox.net>
Date
May 16, 2006, 19:01 UTC
Message-ID
<7vbqtxaj5k.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<m1bqtx6el6.fsf@ebiederm.dsl.xmission.com>
ebiederm@xmission.com (Eric W. Biederman) writes:
Show 8 quoted lines
>    Given the ugliness in -mm making it an error to have an
>    non-attributed patch would result in people specifying --author
>    when they really don't know who the author is, giving us much
>    less reliable information.
>
>    Possibly what we need is an option to not make it an error so that
>    people doing this kind of thing in their own trees have useful
>    information.

I agree it is probably a good way to error by default, optinally allowing to say "don't care". I do not think Linus would pull from such a tree or trees branched from it into his official tree, so I do not think we would need to worry about commits with incomplete information propagating for this particular "gitified mm" usage. But as a general purpose tool to produce "gitified quilt series" tree, we would.

It depends on the expected use of the resulting gitified mm tree.

If it is for an individual developer to futz with and tweak upon, and the end result from the work leaves such a "gitified quilt series" repository only as a patch form, then not having to figure out and specify authorship information to many patches is probably a plus; the information will not be part of the official history recorded elsewhere anyway.

However, if it is to produce a reference git tree to point people at, (i.e. the quiltimport script is run once per a series by somebody and the result is published for public use), I would imagine we would want to have the attribution straight, so if the tool has to "guess", it should either error out or go interactive and ask.

Previous: Eric W. BiedermanNext: Eric W. Biederman
Message 4 of 24 in “Implement git-quiltimport”
  1. Implement git-quiltimportEric W. Biederman, May 16, 2006
  2. Linus TorvaldsMay 16, 2006
  3. Eric W. BiedermanMay 16, 2006
  4. Junio C HamanoMay 16, 2006
  5. Eric W. BiedermanMay 17, 2006
  6. Junio C HamanoMay 17, 2006
  7. Implement git-quiltimport (take 2)Eric W. Biederman, May 17, 2006
  8. Junio C HamanoMay 17, 2006
  9. Eric W. BiedermanMay 17, 2006
  10. Junio C HamanoMay 17, 2006
  11. Eric W. BiedermanMay 18, 2006
  12. Greg KHMay 19, 2006
  13. Eric W. BiedermanMay 20, 2006
  14. Greg KHMay 20, 2006
  15. Eric W. BiedermanMay 21, 2006
  16. Junio C HamanoMay 21, 2006
  17. Eric W. BiedermanMay 21, 2006
  18. Junio C HamanoMay 21, 2006
  19. Eric W. BiedermanMay 21, 2006
  20. Greg KHJun 1, 2006
  21. Eric W. BiedermanJun 2, 2006
  22. Eric W. BiedermanMay 19, 2006
  23. Implement a --dry-run option to git-quiltimportEric W. Biederman, May 17, 2006
  24. Linus TorvaldsMay 17, 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.