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

Re: [PATCH v3] builtin/push: call set_refspecs after validating remote

From
Jeff King <peff@peff.net>
Date
Jul 11, 2024, 21:33 UTC
Message-ID
<20240711213318.GD3648684@coredump.intra.peff.net>
In-Reply-To
<xmqqo774neyj.fsf@gitster.g>
On Thu, Jul 11, 2024 at 08:08:52AM -0700, Junio C Hamano wrote:
Show 6 quoted lines
> > Do a simple fix by doing remote validation first. Also add a test to
> > validate the bug fix. With this, we can also now directly pass remote to
> > 'set_refspecs' instead of it trying to lazily obtain it.
> [..]
> 
> Everything makes sense to me.  Thanks.
Likewise for me.
-Peff
Previous: Junio C Hamano
Message 20 of 20 in “builtin/push: call set_refspecs after validating remote”
  1. builtin/push: call set_refspecs after validating remoteKarthik Nayak, Jul 8, 2024
  2. Junio C HamanoJul 8, 2024
  3. Jeff KingJul 8, 2024
  4. Karthik NayakJul 9, 2024
  5. Jeff KingJul 8, 2024
  6. Karthik NayakJul 9, 2024
  7. Jeff KingJul 9, 2024
  8. builtin/push: call set_refspecs after validating remoteKarthik Nayak, Jul 9, 2024
  9. Junio C HamanoJul 9, 2024
  10. Junio C HamanoJul 9, 2024
  11. Jeff KingJul 9, 2024
  12. Junio C HamanoJul 10, 2024
  13. Karthik NayakJul 10, 2024
  14. Junio C HamanoJul 10, 2024
  15. Jeff KingJul 10, 2024
  16. Karthik NayakJul 11, 2024
  17. Jeff KingJul 11, 2024
  18. builtin/push: call set_refspecs after validating remoteKarthik Nayak, Jul 11, 2024
  19. Junio C HamanoJul 11, 2024
  20. Jeff KingJul 11, 2024

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.