Re: seg fault in "git format-patch"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, May 31, 2015 at 4:53 PM, Christian Couder
<christian.couder@xxxxxxxxx> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]