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

Re: [PATCH v3 1/2] git-gui: use existing interface to query a path's attribute

From
Bert Wesarg <bert.wesarg@googlemail.com>
Date
Oct 2, 2019, 07:35 UTC
Message-ID
<CAKPyHN31qQwL=x0hwk2TjOkyC8iRtcLY0v6NgwA81N2i8P6aBg@mail.gmail.com>
In-Reply-To
<20191001173100.n5dipyhjk4uxcnnj@yadavpratyush.com>
Pratyush,
On Tue, Oct 1, 2019 at 7:31 PM Pratyush Yadav <me@yadavpratyush.com> wrote:
Show 18 quoted lines
>
> On 01/10/19 05:22PM, Bert Wesarg wrote:
> > On Tue, Oct 1, 2019 at 4:24 PM Pratyush Yadav <me@yadavpratyush.com> wrote:
> > >
> > > Hi,
> > >
> > > I don't see any difference between v3 and v2 of this patch. What changed
> > > in this version?
> >
> > nothing, but 2/2 changed.
>
> I don't see a v3 of 2/2 in my inbox. A search on public-inbox yields
> nothing either. Can you please check if the patch was sent properly? Or
> if you _can_ find it on public-inbox.org, a link to that would do just
> fine.
>
> I _do_ have v2 of both patches, but the v3 of the second patch is the
> one missing.

I noticed this already, while in contact with Johannes on GitHub and I found my error. While pasting messages ids for References into the v3 patch, I missed to renamed Message-Id to References for the v2 patch, thus the v3 has the same Message-Id than the v2 patch. Will resend now.

Bert
>
> --
> Regards,
> Pratyush Yadav
Previous: Pratyush YadavNext: Bert Wesarg
Message 5 of 7 in “git-gui: use existing interface to query a path's attribute”
  1. 1/2 git-gui: use existing interface to query a path's attributeBert Wesarg, Sep 30, 2019
  2. Pratyush YadavOct 1, 2019
  3. Bert WesargOct 1, 2019
  4. Pratyush YadavOct 1, 2019
  5. Bert WesargOct 2, 2019
  6. 2/2 git-gui: support for diff3 conflict styleBert Wesarg, Oct 2, 2019
  7. Pratyush YadavOct 2, 2019

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.