git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: bw/remote-rename-update-config, was Re: What's cooking in git.git (Feb 2020, #03; Wed, 12)
Date: Thu, 13 Feb 2020 13:26:34 +0100 (CET)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2002131325580.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqo8u3tqly.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Wed, 12 Feb 2020, Junio C Hamano wrote:

> * bw/remote-rename-update-config (2020-02-10) 6 commits
>  - remote rename/remove: gently handle remote.pushDefault config
>  - config: provide access to the current line number
>  - remote rename/remove: handle branch.<name>.pushRemote config values
>  - remote: clean-up config callback
>  - remote: clean-up by returning early to avoid one indentation
>  - pull --rebase/remote rename: document and honor single-letter abbreviations rebase types
>  (this branch uses mr/show-config-scope; is tangled with es/bugreport.)
>
>  "git remote rename X Y" needs to adjust configuration variables
>  (e.g. branch.<name>.remote) whose value used to be X to Y.
>  branch.<name>.pushRemote is now also updated.
>
>  Will merge to 'next'?

I think so, yes.

Thanks,
Dscho

  reply	other threads:[~2020-02-13 12:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 21:58 What's cooking in git.git (Feb 2020, #03; Wed, 12) Junio C Hamano
2020-02-13 12:26 ` Johannes Schindelin [this message]
2020-02-13 13:02 ` yz/p4-py3, was " Johannes Schindelin
2020-02-13 16:06   ` Junio C Hamano
2020-02-13 21:18     ` Junio C Hamano
2020-02-14  4:17       ` Junio C Hamano
2020-02-14  5:15         ` Denton Liu
2020-02-14 14:39           ` Ben Keene
2020-02-14 16:18             ` Junio C Hamano
2020-02-14 17:01             ` Junio C Hamano
2020-02-14 17:05               ` Ben Keene
2020-02-14 18:10                 ` Junio C Hamano
2020-03-10 17:38       ` SZEDER Gábor
2020-03-10 18:29         ` Junio C Hamano
2020-02-16  4:42 ` Elijah Newren
2020-02-17  7:38   ` Pratyush Yadav

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=nycvar.QRO.7.76.6.2002131325580.46@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).