Re: [PATCH v3 1/2 / RFC] builtin/branch: stop supporting the use of --set-upstream option

Subject: Re: [PATCH v3 1/2 / RFC] builtin/branch: stop supporting the use of --set-upstream option
From: Kaartic Sivaraam <kaarticsivaraam91196@xxxxxxxxx>
Date: Wed, 16 Aug 2017 23:43:09 +0530
Cc: git@xxxxxxxxxxxxxxx, martin.agren@xxxxxxxxx
In-reply-to: <xmqqfucsr73w.fsf@gitster.mtv.corp.google.com>
References: <20170808171136.31168-1-kaarticsivaraam91196@gmail.com> <20170814085442.31174-1-kaarticsivaraam91196@gmail.com> <xmqqy3qluck4.fsf@gitster.mtv.corp.google.com> <772aaebf-81ea-ac22-9d2f-35d0778f502f@gmail.com> <xmqqfucsr73w.fsf@gitster.mtv.corp.google.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1

On Wednesday 16 August 2017 12:28 AM, Junio C Hamano wrote:

Some refactoring to make it easier to reuse it from the new callerwould be necessary.

Sorry but I think I don't get that correctly. What's the "new caller"being referred to here?

What should be refactored?

---
Kaartic

Follow-Ups:
- Re: [PATCH v3 1/2 / RFC] builtin/branch: stop supporting the use of --set-upstream option
  - From: Junio C Hamano

References:
- [PATCH v2 1/2 / RFC] builtin/branch: stop supporting the use of --set-upstream option
  - From: Kaartic Sivaraam
- [PATCH v3 1/2 / RFC] builtin/branch: stop supporting the use of --set-upstream option
  - From: Kaartic Sivaraam
- Re: [PATCH v3 1/2 / RFC] builtin/branch: stop supporting the use of --set-upstream option
  - From: Junio C Hamano
- Re: [PATCH v3 1/2 / RFC] builtin/branch: stop supporting the use of --set-upstream option
  - From: Kaartic Sivaraam
- Re: [PATCH v3 1/2 / RFC] builtin/branch: stop supporting the use of --set-upstream option
  - From: Junio C Hamano