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

Re: [PATCH 1/2] am: preliminary support for hg patches

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 30, 2011, 17:02 UTC
Message-ID
<7vwrdu3ka0.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAOxFTczyNtyLWyXppj=0UW_zeD3t+rDtzt-vwqXkwvWOTdxi2g@mail.gmail.com>
Giuseppe Bilotta <giuseppe.bilotta@gmail.com> writes:
Show 17 quoted lines
> ... This is
> correctly detected by -3, with
>
> Applying: Threeway test
> fatal: sha1 information is lacking or useless (dir.h).
> Repository lacks necessary blobs to fall back on 3-way merge.
> Cannot fall back to three-way merge.
> Patch failed at 0001 Threeway test
>
> The message is a bit misleading (it's not the repo lacking the blobs,
> it's the patch missing the information), but the process fails as
> expected.
>
>> What about renaming patches?
>
> They lack similarity indices, but they seem to be properly formated
> (and the simple cases I tested apply correctly).
These were exactly what I wanted to know. Thanks for experimenting.
> So I think that keeping the --git is the right choice.
Yeah, sounds like we are safe and better off keeping it.
Previous: Giuseppe BilottaNext: Sverre Rabbelier
Message 7 of 9 in “am: foreign patch support fixes”
  1. 0/2 am: foreign patch support fixesGiuseppe Bilotta, Aug 29, 2011
  2. 1/2 am: preliminary support for hg patchesGiuseppe Bilotta, Aug 29, 2011
  3. Junio C HamanoAug 29, 2011
  4. Giuseppe BilottaAug 29, 2011
  5. Junio C HamanoAug 29, 2011
  6. Giuseppe BilottaAug 30, 2011
  7. Junio C HamanoAug 30, 2011
  8. Sverre RabbelierAug 31, 2011
  9. 2/2 am: fix stgit patch manglingGiuseppe Bilotta, Aug 29, 2011

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.