Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow vendors to customize the version info #3636

Merged
merged 1 commit into from
May 15, 2019
Merged

Conversation

bk2204
Copy link
Member

@bk2204 bk2204 commented May 8, 2019

It's common for vendors (such as Linux distros) to want to customize the User-Agent string and version information for software they provide. This is valuable for vendors, but it also allows troubleshooting problems with custom patches that may have been applied by the vendor. Allow vendors to set a VENDOR makefile flag to set the vendor field for the User-Agent and version information.

@bk2204 bk2204 requested a review from a team May 8, 2019 18:45
It's common for vendors (such as Linux distros) to want to customize the
User-Agent string and version information for software they provide.
This is valuable for vendors, but it also allows troubleshooting
problems with custom patches that may have been applied by the vendor.
Allow vendors to set a VENDOR makefile flag to set the vendor field for
the User-Agent and version information.
Copy link
Contributor

@PastelMobileSuit PastelMobileSuit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bk2204 bk2204 merged commit ffc85f6 into git-lfs:master May 15, 2019
@bk2204 bk2204 deleted the vendor branch May 15, 2019 21:20
@QuLogic
Copy link
Contributor

QuLogic commented Aug 18, 2019

Do you have any expectations of what to put in this field?

@bk2204
Copy link
Member Author

bk2204 commented Aug 19, 2019

The default is "GitHub", and I had anticipated an alternative such as "Debian" or "Fedora". If, for example, SourceTree were distributing their own version, they could use "Atlassian", "SourceTree", or "Atlassian SourceTree".

I just know that Debian often wants to customize these kinds of fields, so I provided a technique for them to do so should they want to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants