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

Re: [PATCH v5 02/14] trailer: process trailers from file and arguments

From
Christian Couder <chriscool@tuxfamily.org>
Date
Feb 10, 2014, 19:59 UTC
Message-ID
<20140210.205936.813126606054805390.chriscool@tuxfamily.org>
In-Reply-To
<xmqq61omu96d.fsf@gitster.dls.corp.google.com>
From: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v5 02/14] trailer: process trailers from file and arguments
Date: Mon, 10 Feb 2014 10:14:34 -0800
Show 25 quoted lines
> Christian Couder <chriscool@tuxfamily.org> writes:
> 
>> This is what "if_exists" and "if_missing" are all about.
>>
>> Either:
>>
>> 	the same key already exists regardless of the value
>>
>> and, in this case, what happens depends on what has been specified using
>> the "if_exists" configuration variable.
>>
>> Or:
>>
>> 	the same key DOES NOT already exists regardless of the value
>>
>> and in this case, what happens depends on what has been specified
>> using the "if_missing" configuration variable.
> 
> Hmm, how should things like signed-off-by be handled?  You may want
> to allow many entries with the same key with distinct values, but
> duplicated values may want to be handled differently (currently we
> only avoid to place a duplicate <key, value> consecutively, but keys
> with different semantics (e.g. "fixes-bug: #bugid") may want to say
> "unless the same key with the same value exists, append it at the
> end".

Many entries with the same key but distinct values can be configured using:

if_exists = add_if_different if_missing = add

Many entries with the same key but values that can be the same can be configured using:

if_exists = add if_missing = add

The place where the trailers are added, if they should be added, can be selected using either "where = after", the default, or "where = before".

"where = after" means just after trailers with the same key, or, if there are no trailers with the same key, after all the existing trailers.

"where = before" means just before trailers with the same key, or, if there are no trailers with the same key, before all the existing trailers.

I think that this is enough to handle most of the usual cases, but we can add other more complex options later, as I said in the last message of this thread:

http://thread.gmane.org/gmane.comp.version-control.git/237278/

Thanks, Christian.

Previous: Junio C HamanoNext: Junio C Hamano
Message 12 of 48 in “Add interpret-trailers builtin”
  1. 00/14 Add interpret-trailers builtinChristian Couder, Feb 6, 2014
  2. 01/14 Add data structures and basic functions for commit trailersChristian Couder, Feb 6, 2014
  3. Junio C HamanoFeb 6, 2014
  4. Christian CouderFeb 9, 2014
  5. Eric SunshineFeb 10, 2014
  6. Junio C HamanoFeb 6, 2014
  7. Christian CouderFeb 9, 2014
  8. 02/14 trailer: process trailers from file and argumentsChristian Couder, Feb 6, 2014
  9. Junio C HamanoFeb 7, 2014
  10. Christian CouderFeb 9, 2014
  11. Junio C HamanoFeb 10, 2014
  12. Christian CouderFeb 10, 2014
  13. Junio C HamanoFeb 10, 2014
  14. Christian CouderFeb 11, 2014
  15. Junio C HamanoFeb 11, 2014
  16. Christian CouderFeb 14, 2014
  17. Junio C HamanoFeb 14, 2014
  18. Christian CouderFeb 14, 2014
  19. Junio C HamanoFeb 14, 2014
  20. Junio C HamanoFeb 14, 2014
  21. Junio C HamanoFeb 15, 2014
  22. Junio C HamanoFeb 21, 2014
  23. Christian CouderFeb 23, 2014
  24. 03/14 trailer: read and process config informationChristian Couder, Feb 6, 2014
  25. 04/14 trailer: process command line trailer argumentsChristian Couder, Feb 6, 2014
  26. Junio C HamanoFeb 7, 2014
  27. Christian CouderFeb 9, 2014
  28. 05/14 trailer: parse trailers from input fileChristian Couder, Feb 6, 2014
  29. 06/14 trailer: put all the processing together and printChristian Couder, Feb 6, 2014
  30. 07/14 trailer: add interpret-trailers commandChristian Couder, Feb 6, 2014
  31. Junio C HamanoFeb 7, 2014
  32. Christian CouderFeb 7, 2014
  33. Junio C HamanoFeb 7, 2014
  34. Junio C HamanoFeb 7, 2014
  35. 08/14 trailer: add tests for "git interpret-trailers"Christian Couder, Feb 6, 2014
  36. Junio C HamanoFeb 7, 2014
  37. 09/14 trailer: if no input file is passed, read from stdinChristian Couder, Feb 6, 2014
  38. Junio C HamanoFeb 7, 2014
  39. 10/14 trailer: execute command from 'trailer.<name>.command'Christian Couder, Feb 6, 2014
  40. Junio C HamanoFeb 7, 2014
  41. Junio C HamanoFeb 7, 2014
  42. 11/14 trailer: add tests for trailer commandChristian Couder, Feb 6, 2014
  43. 12/14 trailer: set author and committer env variablesChristian Couder, Feb 6, 2014
  44. Junio C HamanoFeb 7, 2014
  45. Junio C HamanoFeb 7, 2014
  46. 13/14 trailer: add tests for commands using env variablesChristian Couder, Feb 6, 2014
  47. 14/14 Documentation: add documentation for 'git interpret-trailers'Christian Couder, Feb 6, 2014
  48. Eric SunshineFeb 10, 2014

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.