All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Will Deacon <will@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: b4 ty not picking up per-remote git config properties
Date: Thu, 7 May 2020 13:37:50 -0400	[thread overview]
Message-ID: <20200507173750.jvd6kvatmon36pa2@chatter.i7.local> (raw)
In-Reply-To: <20200507114255.GB29541@willie-the-truck>

On Thu, May 07, 2020 at 12:42:56PM +0100, Will Deacon wrote:
> Hi Konstantin,
> 
> I've been having trouble persuading 'b4 ty' to honour the 'b4-treename'
> and 'b4-commit-url-mask' properties if they are specified on a per-remote
> basis. This seems to be because get_branch_info() has expectations about
> branch naming to which I'm probably not adhering.
> 
> In my specific case, I have a branch called 'for-joerg/arm-smmu/updates'
> which has a remote called 'wd-korg', so my .git/config contains:
> 
> [remote "wd-korg"]
> 	...
> 	b4-treename = will
> 	b4-commit-url-mask = https://git.kernel.org/will/c/%.12s
> 
> [branch "for-joerg/arm-smmu/updates"]
> 	remote = wd-korg
> 	merge = refs/heads/for-joerg/arm-smmu/updates
> 
> but 'b4 ty' always takes the properties from my top-level .gitconfig.
> 
> I've hacked ty.py as below to get things working but, believe it or not,
> this is the first time I've written any python so I suspect it's all a
> load of rubbish.

It's not, I used it largely without changes. The latest master and 
stable-0.4.y should be a lot less naive about local and remote branch 
names.

Best,
-K

  reply	other threads:[~2020-05-07 17:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 11:42 b4 ty not picking up per-remote git config properties Will Deacon
2020-05-07 17:37 ` Konstantin Ryabitsev [this message]
2020-05-11 15:03   ` Will Deacon

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=20200507173750.jvd6kvatmon36pa2@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=tools@linux.kernel.org \
    --cc=will@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 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.