tl;dr: This patch series wants to introduce a permanent new Git data
format. The current version can write trailers in formats that it is
incapable of reading, which I consider broken. I advocate a stricter
specification of the format of trailers, at least until we get feedback
from users that
On Tue, May 27, 2014 at 10:21 AM, Michael Haggerty mhag...@alum.mit.edu wrote:
tl;dr: This patch series wants to introduce a permanent new Git data
format. The current version can write trailers in formats that it is
incapable of reading, which I consider broken. I advocate a stricter
Christian Couder chrisc...@tuxfamily.org writes:
From: Michael Haggerty mhag...@alum.mit.edu
...
An option like --input-separator might be enough to support this.
For me this means:
* Enumerating a list of allowed separators (e.g., [:=#])
Junio suggested in a message that users might
From: Michael Haggerty mhag...@alum.mit.edu
On 04/25/2014 11:07 PM, Christian Couder wrote:
I don't think there is a lot of complexity.
But maybe I need to explain how it works better.
Feel free to suggest me sentences I could add.
I am really excited about having better support for
From: Jeremy Morton ad...@game-point.net
On 29/04/2014 12:47, Christian Couder wrote:
Also, if there were no current branch name because you're committing
in a
detached head state, it would be nice if you could have some logic to
determine that, and instead write the trailer as:
On 28/04/2014 17:37, Junio C Hamano wrote:
Christian Couderchrisc...@tuxfamily.org writes:
From: Junio C Hamanogits...@pobox.com
Christian Couderchrisc...@tuxfamily.org writes:
...
+ trailer. After some alphanumeric characters, it can contain
+ some non alphanumeric
On Tue, Apr 29, 2014 at 1:05 PM, Jeremy Morton ad...@game-point.net wrote:
On 28/04/2014 17:37, Junio C Hamano wrote:
Christian Couderchrisc...@tuxfamily.org writes:
From: Junio C Hamanogits...@pobox.com
Christian Couderchrisc...@tuxfamily.org writes:
...
+ trailer. After some
On 29/04/2014 12:47, Christian Couder wrote:
Also, if there were no current branch name because you're committing in a
detached head state, it would be nice if you could have some logic to
determine that, and instead write the trailer as:
Made-on-branch: (detached HEAD: AB12CD34)
You
On 29/04/2014 12:47, Christian Couder wrote:
Also, if there were no current branch name because you're committing in a
detached head state, it would be nice if you could have some logic to
determine that, and instead write the trailer as:
Made-on-branch: (detached HEAD: AB12CD34)
You
On 04/25/2014 11:07 PM, Christian Couder wrote:
From: Michael Haggerty mhag...@alum.mit.edu
+OPTIONS
+---
+--trim-empty::
+ If the 'value' part of any trailer contains only whitespace,
+ the whole trailer will be removed from the resulting message.
Does this apply to existing
Christian Couder chrisc...@tuxfamily.org writes:
From: Junio C Hamano gits...@pobox.com
Christian Couder chrisc...@tuxfamily.org writes:
...
+ trailer. After some alphanumeric characters, it can contain
+ some non alphanumeric characters like ':', '=' or '#' that will
+ be used
From: Junio C Hamano gits...@pobox.com
Christian Couder chrisc...@tuxfamily.org writes:
+Help add RFC 822-like headers, called 'trailers', at the end of the
+otherwise free-form part of a commit message.
I think it is somewhat misleading to use the word headers like
that. 'trailers'
From: Michael Haggerty mhag...@alum.mit.edu
On 04/08/2014 01:35 PM, Christian Couder wrote:
The trailers are recognized in the input commit message using the
following rules:
- only lines that contains a ':' are considered trailers,
- the trailer lines must all be next to each other,
-
Sorry for reappearing in this thread after such a long absence. I
wanted to see what is coming up (I think this interpret-trailers command
will be handy!) so I read this documentation patch carefully, and added
some questions and suggestions below.
On 04/06/2014 07:02 PM, Christian Couder wrote:
On Tue, Apr 8, 2014 at 9:30 AM, Michael Haggerty mhag...@alum.mit.edu wrote:
+This command is a filter. It reads the standard input for a commit
+message and applies the `token` arguments, if any, to this
+message. The resulting message is emited on the standard output.
s/emited/emitted/
On 04/08/2014 01:35 PM, Christian Couder wrote:
On Tue, Apr 8, 2014 at 9:30 AM, Michael Haggerty mhag...@alum.mit.edu wrote:
How are existing trailers recognized in the input commit message? Do
trailers have to be configured to be recognized? Or are all lines
matching a specific pattern
Michael Haggerty mhag...@alum.mit.edu writes:
Sorry for reappearing in this thread after such a long absence. I
wanted to see what is coming up (I think this interpret-trailers command
will be handy!) so I read this documentation patch carefully, and added
some questions and suggestions
Christian Couder chrisc...@tuxfamily.org writes:
+Help add RFC 822-like headers, called 'trailers', at the end of the
+otherwise free-form part of a commit message.
I think it is somewhat misleading to use the word headers like
that. 'trailers' look similar to RFC-822-headers but they come at
18 matches
Mail list logo
