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

Re: [BUG] git cherry-pick segfaults with local changes in working directory

From
Jeff King <peff@peff.net>
Date
Jun 15, 2017, 13:03 UTC
Message-ID
<20170615130331.tak725h2i3fe7npw@sigill.intra.peff.net>
In-Reply-To
<1497523056.2239.107.camel@centricular.com>
On Thu, Jun 15, 2017 at 01:37:36PM +0300, Sebastian Dröge wrote:
Show 6 quoted lines
> > Note that the tarball doesn't have all the necessary objects. Its
> > .git/objects/info/alternates points to another full clone of
> > git://anongit.freedesktop.org/gstreamer/gst-plugins-good.
> 
> Ah good to know, I thought this only happens if you clone with
> --reference and not otherwise.

If you do a local-filesystem clone of a repository with alternates, the clone will have the same alternates. So I'm guessing you may have done such a clone of your --reference repository as part of preparing the tarball.

-Peff
Previous: Sebastian Dröge
Message 4 of 4 in “[BUG] git cherry-pick segfaults with local changes in working directory”
  1. Sebastian DrögeJun 15, 2017
  2. Jeff KingJun 15, 2017
  3. Sebastian DrögeJun 15, 2017
  4. Jeff KingJun 15, 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.