From: Andreas Schwab <schwab@suse.de>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Florian Weimer <fweimer@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
DJ Delorie <dj@redhat.com>
Subject: Re: [PATCH v4] libc: Extend __libc_freeres framework (Bug 23329).
Date: Thu, 28 Jun 2018 19:03:00 -0000 [thread overview]
Message-ID: <mvmk1qj0z38.fsf@suse.de> (raw)
In-Reply-To: <22cd6fb5-87ed-ffe1-79ad-d693f44a99f4@redhat.com> (Carlos O'Donell's message of "Thu, 28 Jun 2018 10:13:30 -0400")
On Jun 28 2018, Carlos O'Donell <carlos@redhat.com> wrote:
> On 06/28/2018 09:44 AM, Florian Weimer wrote:
>> On 06/28/2018 03:35 PM, Carlos O'Donell wrote:
>>> This is the only commit I have on top of master.
>>>
>>> Where are the conflicts?
>>
>> git am cannot construct a common ancestor because it doesn't have a copy of the original file:
>>
>> diff --git a/ChangeLog b/ChangeLog
>> index 1f35f29d77..5f34833c2c 100644
>>
>> Locally, I do not have a blob starting with 1f35f29d77, with master at commit 0b11b6491cc01b5ce5fea1302f8591f25e8c4d80.
>
> I don't have it either, but git format-patch HEAD~2 still generates it.
It's a blob, not a commit. Try git show 1f35f29d77.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-06-28 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 3:06 [PATCH] " Carlos O'Donell
2018-06-27 9:46 ` Florian Weimer
2018-06-28 4:15 ` [PATCH v2] " Carlos O'Donell
2018-06-28 12:13 ` Florian Weimer
2018-06-28 13:07 ` [PATCH v3] " Carlos O'Donell
2018-06-28 13:22 ` Florian Weimer
2018-06-28 13:36 ` [PATCH v4] " Carlos O'Donell
2018-06-28 13:44 ` Florian Weimer
2018-06-28 14:13 ` Carlos O'Donell
2018-06-28 14:15 ` Florian Weimer
2018-06-28 14:26 ` Carlos O'Donell
2018-06-28 14:50 ` Florian Weimer
2018-06-28 19:03 ` Andreas Schwab [this message]
2018-06-28 19:10 ` Florian Weimer
2018-07-02 8:56 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mvmk1qj0z38.fsf@suse.de \
--to=schwab@suse.de \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).