Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: "Mark Brown" <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: b4 ty feature requests
Date: Fri, 17 Apr 2020 18:09:04 +0100	[thread overview]
Message-ID: <20200417170904.GI5315@sirena.org.uk> (raw)
In-Reply-To: <20200417165537.4xgdj537vw26fai6@chatter.i7.local>

[-- Attachment #1: Type: text/plain, Size: 885 bytes --]

On Fri, Apr 17, 2020 at 12:55:37PM -0400, Konstantin Ryabitsev wrote:

> Ah, excellent data point. How about we approach it from a slightly 
> different angle. We already allow setting a per-repo 
> "thanks-commit-url-mask", but how about also a way to record that in the 
> remote section of .git/config, e.g.:

> [remote "foo"]
>   url = git@gitolite.kernel.org:pub/scm/linux/kernel/git/foo/linux
>   fetch = +refs/heads/*:refs/remotes/foo/*
>   b4-treename = "foo/linux.git"
>   b4-commit-url-mask = "https://git.kernel.org/foo/c/%.8s"

> Would that work?

I think so, yes - the treename could even default to either url or the
remote name so a lot of the time it'd not even need to be set.

One thing to watch out for is that you can name branches foo/bar without
them being remotes so just because there's a / that doesn't mean the
branch is a remote branch.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

  reply	other threads:[~2020-04-17 17:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 15:44 b4 ty feature requests Mark Brown
2020-04-17 16:14 ` Konstantin Ryabitsev
2020-04-17 16:39   ` Mark Brown
2020-04-17 16:55     ` Konstantin Ryabitsev
2020-04-17 17:09       ` Mark Brown [this message]
2020-04-17 19:06         ` Konstantin Ryabitsev
2020-04-20 15:46           ` Mark Brown
2020-04-20 17:03             ` Konstantin Ryabitsev

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=20200417170904.GI5315@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@linux.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox