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

Re: issues(?) installing git-lfs via fedora "dnf" command

From
Jonathan Nieder <jrnieder@gmail.com>
Date
May 21, 2018, 17:14 UTC
Message-ID
<20180521171405.GB10623@aiede.svl.corp.google.com>
In-Reply-To
<alpine.LFD.2.21.1805211303260.19892@localhost.localdomain>
Hi,
Robert P. J. Day wrote:
> On Mon, 21 May 2018, Jonathan Nieder wrote:
Show 11 quoted lines
>> The packager should be able to find out whether it's an issue in
>> git-lfs upstream and report it to that project if it is.  Git-lfs is
>> not part of git.git; it's a separate project:
>> https://github.com/git-lfs/git-lfs/blob/master/CONTRIBUTING.md
>> I believe they use github's issue tracker to track bugs.
>
>   it would *appear* that this is a combination of both a git issue,
> and a red hat packaging issue:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1580357
> https://github.com/git-lfs/git-lfs/issues/3013

Can you clarify? Neither of those bugs points to a git issue if I understand correctly. They may be a git-lfs issue, though.

This kind of confusion is exactly why the Git project adopted a trademark policy to prevent outside projects from identifying themselves with Git: https://git-scm.com/about/trademark. Unfortunately Git LFS's existence precedes that policy. I believe they got permission to continue using the name, confusing as it is.

Thanks, Jonathan

Previous: Robert P. J. DayNext: Robert P. J. Day
Message 4 of 5 in “issues(?) installing git-lfs via fedora "dnf" command”
  1. Robert P. J. DayMay 21, 2018
  2. Jonathan NiederMay 21, 2018
  3. Robert P. J. DayMay 21, 2018
  4. Jonathan NiederMay 21, 2018
  5. Robert P. J. DayMay 21, 2018

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.