All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	Li Chen <me@linux.beauty>, Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [RFC PATCH 1/2] rebase, am: add --reviewby option
Date: Wed, 7 May 2025 14:38:47 +0100	[thread overview]
Message-ID: <67417874-d22a-40bf-b35e-4aaaefe6d2b5@gmail.com> (raw)
In-Reply-To: <fdf7a827-d8ca-4edc-8427-a2c6eb470e1a@app.fastmail.com>

On 07/05/2025 11:39, Kristoffer Haugsbakk wrote:
> On Wed, May 7, 2025, at 12:26, Phillip Wood wrote:
> 
>> It might be worth thinking about how we could extend the trailer option
>> so that it uses the committer identity if there is no value specified
>> which would reduce the pain of adding things like Reviewed-by:
> 
> That could be confusing for people who use trailers for
> non-ident metadata.

Yes we need to think about how to do it in a way that is helpful for 
things like Reviewed-by: or Tested-by: but does not break other 
workflows. One possibility would be to have a 
trailer.<name>.defaultValue config key but I'd be interested in other 
people's ideas.

One other idea is that "git commit --author Kristoffer" will search 
recent commits for matching author to obtain your full name and email 
address. Something like that could be useful for expanding values 
--tailer=Co-Authored-by" or perhaps we could teach the completion script 
to suggest suitable completions based on some config describing the 
values we expect for certain keys.

> I was wondering if `git var GIT_COMMITTER_IDENT` could be used.  But
> that prints a Unix timestamp with timezone as well. (I don’t really
> understand why after reading that part of the manual)
> 
I think it is because with define GIT_*_IDENT to include the timestamp 
to match the ident lines in commit and tag objects. You can always trim 
the timestamp appending something like "| sed 's/[^>]*$//'".

Best Wishes

Phillip

  reply	other threads:[~2025-05-07 13:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 12:57 [RFC PATCH 0/2] rebase: support --trailer and add --reviewby Li Chen
2025-05-06 12:58 ` [RFC PATCH 1/2] rebase, am: add --reviewby option Li Chen
2025-05-06 18:07   ` Junio C Hamano
2025-05-07  6:46     ` Li Chen
2025-05-07 10:17       ` Phillip Wood
2025-05-07 10:26         ` Phillip Wood
2025-05-07 10:39           ` Kristoffer Haugsbakk
2025-05-07 13:38             ` Phillip Wood [this message]
2025-05-07 17:39         ` Junio C Hamano
2025-05-06 12:58 ` [RFC PATCH 2/2] rebase: support --trailer Li Chen
2025-05-08 14:17   ` Phillip Wood
2025-05-08 15:55     ` Li Chen
2025-05-08 15:58       ` phillip.wood123
2025-05-08 16:29       ` Phillip Wood
2025-05-16  5:42     ` Li Chen
2025-05-16 10:04       ` Phillip Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=67417874-d22a-40bf-b35e-4aaaefe6d2b5@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=me@linux.beauty \
    --cc=phillip.wood@dunelm.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.