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

Re: seg fault in "git format-patch"

From
Bruce Korb <bruce.korb@gmail.com>
Date
Jun 1, 2015, 14:47 UTC
Message-ID
<CAKRnqNKWb5upY5Xm07UgJvk5SfPVdAWhR=MFkAbRDy4RFaLxRQ@mail.gmail.com>
In-Reply-To
<CAP8UFD0_RCOHUF6BgczgS5kWAFc0QKdw4cUy_bpB2jhd+kYWdw@mail.gmail.com>

On Sun, May 31, 2015 at 4:53 PM, Christian Couder <christian.couder@gmail.com> wrote:

>> (Please don't top post if you reply to this email as it is frown upon
>> on this list.)
WRT "top posting", two points:
1. Too many sites/lists now *require* top posting
2. MUA's (like Google Mail) hide the old mail as an obscure squiggle
at the bottom of the page.

Time to just get over it and accept the fact that there are two conventions. I did. I only gave up a decade ago.

> $ git format-patch -o patches --ignore-if-in-upstream
> 14949fa8f39d29e44b43f4332ffaf35f11546502..2de9eef391259dfc8748dbaf76a5d55427f37b0d
>
> It is interesting to note that the last sha1 refers to a tag:

They both do. I tried "git format-patch v1.3..v1.4" but that didn't work and I knew that SHA1..SHA2 would, so I got the SHA's for the tags.

> It works when the tag is replaced by the commit it points to, and the
> segfault happens because the we try to access the "parents" field of
> the tag object as if it was a commit.
The other discussion started *after* this one, but thanks for the pointer.
Previous: Christian Couder
Message 21 of 21 in “seg fault in "git format-patch"”
  1. Bruce KorbMay 31, 2015
  2. Christian CouderMay 31, 2015
  3. Bruce KorbMay 31, 2015
  4. Bruce KorbMay 31, 2015
  5. Christian CouderMay 31, 2015
  6. Christian CouderMay 31, 2015
  7. Christian CouderJun 1, 2015
  8. format-patch: dereference tags with --ignore-if-in-upstreambrian m. carlson, Jun 1, 2015
  9. Jeff KingJun 1, 2015
  10. brian m. carlsonJun 1, 2015
  11. Jeff KingJun 1, 2015
  12. Junio C HamanoJun 1, 2015
  13. Junio C HamanoJun 1, 2015
  14. Jeff KingJun 1, 2015
  15. Junio C HamanoJun 1, 2015
  16. brian m. carlsonJun 1, 2015
  17. Junio C HamanoJun 1, 2015
  18. Junio C HamanoJun 1, 2015
  19. Christian CouderJun 1, 2015
  20. Christian CouderJun 1, 2015
  21. Bruce KorbJun 1, 2015

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.