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

Re: [PATCH v2] branch: improve error log on branch not found by checking remotes refs

From
Clement Mabileau <mabileau.clement@gmail.com>
Date
Apr 4, 2023, 13:30 UTC
Message-ID
<ff7bb1f4-e35a-66ad-1116-6bb2b906fed3@gmail.com>
In-Reply-To
<cffce108-c39d-f13f-9fb6-60624f7e7cea@gmail.com>
On 3/23/23 16:51, Clement Mabileau wrote:
Show 32 quoted lines
>
> Well maybe it got it from the original commit or from my GitHub
> username, I can't know for sure. But sorry for that :/ , I'll make
> sure it's fixed it for potential future contribution!
>
> Before fixing anything about the code maybe I should first address your
> last point which is the interest of the patch in the first place (and I
> should have started with that...).
>
> A few months earlier, for the first time, I had to delete a remote ref
> (because of a fork I fetched but no longer wanted: maybe a designed
> solution exists but I'm not aware of it). However, despite being used to
> git I had a hard time figuring out how to do it, I tried different
> things, one was `git branch -d origin/<branch>` (I recently discovered
> that it was written in `git branch --help` but I didn't find it at the
> time). Even googling it proved difficult (because of a poor keyword
> choice I must confess), most results was dealing with deleting remote
> branches, such as `git push remote :branch`.
> In the end, I finally understood that I needed that `--remote` flag and
> really regretted that there wasn't an hint message to head me towards
> the solution when I was getting close to it.
>
> Now I hope you'll understand why I suggested this patch. Maybe I'm the
> only one that ended up in this situation, in this case I'd understand
> that you would no longer be interested in the patch!
> However if you still are, I'll be happy to make the modification you
> asked for.
>
>
> Yeah probably, I'll fix it along with the other.
>
> Thanks for reviewing this!

Well, it would be nice to have an answer in order to know if I should abandon this patch or not :) Thanks!

Previous: Clement MabileauNext: Junio C Hamano
Message 10 of 13 in “branch: improve error log on branch not found by checking remotes refs”
  1. 0/2 branch: improve error log on branch not found by checking remotes refsClementMabileau via GitGitGadget, Mar 22, 2023
  2. 2/2 Fix mem leak in branch.c due to not-free newly added virtual_name variablectmbl via GitGitGadget, Mar 22, 2023
  3. Junio C HamanoMar 22, 2023
  4. Clement MabileauMar 22, 2023
  5. Junio C HamanoMar 22, 2023
  6. 1/2 branch: improve error log on branch not found by checking remotes refsctmbl via GitGitGadget, Mar 22, 2023
  7. branch: improve error log on branch not found by checking remotes refsClementMabileau via GitGitGadget, Mar 22, 2023
  8. Junio C HamanoMar 22, 2023
  9. Clement MabileauMar 23, 2023
  10. Clement MabileauApr 4, 2023
  11. Junio C HamanoApr 4, 2023
  12. Clement MabileauApr 5, 2023
  13. branch: improve error log on branch not found by checking remotes refsClementMabileau via GitGitGadget, Apr 5, 2023

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.