git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 9, 2017, 05:09 UTC
Message-ID
<xmqqy3xgrlvh.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170209034657.qbkzbbzuvjpxl422@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 25 quoted lines
> On Mon, Feb 06, 2017 at 02:34:08PM -0800, Junio C Hamano wrote:
>
>> * sk/parse-remote-cleanup (2017-02-06) 1 commit
>>   (merged to 'next' on 2017-02-06 at 6ec89f72d5)
>>  + parse-remote: remove reference to unused op_prep
>> 
>>  Code clean-up.
>> 
>>  Will merge to 'master'.
>
> Hrm. Are the functions in git-parse-remote.sh part of the public API?
> That is, do we expect third-party scripts to do:
>
>   . "$(git rev-parse --exec)/git-parse-remote.sh
>   error_on_missing_default_upstream "$a" "$b" "$c" "$d"
>
> ? If so, then they may be surprised by the change in function signature.
>
> I generally think of git-sh-setup as the one that external scripts would
> use. There _is_ a manpage for git-parse-remote, but it doesn't list any
> functions. So maybe they're all fair game for changing?
>
> I just didn't see any discussion of this in the original patch thread,
> so I wanted to make sure we were making that decision consciously, and
> not accidentally. :)

Ummm, yes, I admit that this was accidental. I didn't really think of parse-remote as an externally visible and supported interface, but users have tendency to break our expectations, so, I dunno.

Previous: Jeff KingNext: Junio C Hamano
Message 8 of 17 in “What's cooking in git.git (Feb 2017, #02; Mon, 6)”
  1. Junio C HamanoFeb 6, 2017
  2. SZEDER GáborFeb 7, 2017
  3. Jacob KellerFeb 7, 2017
  4. Junio C HamanoFeb 7, 2017
  5. Stefan BellerFeb 9, 2017
  6. Junio C HamanoFeb 9, 2017
  7. Jeff KingFeb 9, 2017
  8. Junio C HamanoFeb 9, 2017
  9. Junio C HamanoFeb 10, 2017
  10. Johannes SchindelinFeb 9, 2017
  11. Junio C HamanoFeb 9, 2017
  12. Johannes SchindelinFeb 9, 2017
  13. Junio C HamanoFeb 9, 2017
  14. Johannes SchindelinFeb 9, 2017
  15. Michael HaggertyFeb 9, 2017
  16. Junio C HamanoFeb 9, 2017
  17. Junio C HamanoFeb 9, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.