From: Usman Akinyemi <usmanakinyemi202@gmail.com>
To: rsbecker@nexbridge.com
Cc: gitster@pobox.com, Johannes.Schindelin@gmx.de,
christian.couder@gmail.com, git@vger.kernel.org,
johncai86@gmail.com, ps@pks.im
Subject: Re: [PATCH 0/3] Advertise OS version
Date: Wed, 11 Dec 2024 00:21:59 +0530 [thread overview]
Message-ID: <CAPSxiM8hYPAuZhiTX06jmw7FRr0_6P5+4WjudM9Ad84Lid6gDA@mail.gmail.com> (raw)
In-Reply-To: <00e201db4a58$3b198fb0$b14caf10$@nexbridge.com>
On Mon, Dec 9, 2024 at 10:04 PM <rsbecker@nexbridge.com> wrote:
>
> On December 9, 2024 11:15 AM, Usman Akinyemi wrote:
> >Thank you to everyone who participated in this discussion. I am Usman Akinyemi,
> >one of the two selected Outreachy interns. I have been selected to work on the
> >project “Finish adding an 'os-version'
> >capability to Git protocol v2,” which involves implementing the features discussed in
> >this thread.
> >
> >You can find the full discussion about my proposal for this project
> >here: https://public-inbox.org/git/CAPSxiM_rvt-tkQjHYmYNv-
> >Wyr0=X4+123dt=vZKtc++PGRjQMQ@mail.gmail.com/
> >
> >In summary, this is an outline of my proposal and what I plan to implement, which
> >has been influenced by the discussion in this thread:
> >
> >- Send only the OS name by default while allowing a knob (custom
> >configuration) to specify other information (e.g., version details) and disable
> >sending OS names and any other information entirely.
> >
> >After discussing with my mentor, @Christian, we think that adding this as a new
> >capability (os-version) is a better option compared to appending it to the user-
> >agent. This ensures that we do not disrupt people's scripts that collect statistics
> >from the user-agent or perform other actions.
> >
> >Intentions of implementing this project:
> >- For statistical purposes.
> >- Most importantly, for security and debugging purposes. This will allow servers to
> >instruct users to upgrade or perform specific debugging actions when necessary.
> >
> >For example:-
> >A server seeing that a client is using an old Git version that has security issues on
> >one platform, like MacOS, could check if the user is indeed running MacOS before
> >sending it a message to upgrade.
> >
> >Also a server seeing a client that could benefit from an upgrade, for example for
> >performance reasons, could better customize the message it sends to the client to
> >nudge it to upgrade. If the client is on Windows for example the server could send it
> >a link to https://gitforwindows.org/ as part of the message.
> >
> >Please, if anyone has any suggestion or addition or concerns that might, kindly add.
> >Thank you very much.
>
Hello Randall,
> Is this build-time or runtime? If run-time, please make sure the code is portable or provides
> hooks so that non-linux systems can contribute content.
>
Thanks for pointing this out.
Yeah, the aim is to have it at runtime and to have hooks that can be
used by non-linux systems.
Thank you.
Usman.
> Thanks,
> Randall
>
> --
> Brief whoami: NonStop&UNIX developer since approximately
> UNIX(421664400)
> NonStop(211288444200000000)
> -- In real life, I talk too much.
>
>
>
prev parent reply other threads:[~2024-12-10 18:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 12:57 [PATCH 0/3] Advertise OS version Christian Couder
2024-06-19 12:57 ` [PATCH 1/3] version: refactor strbuf_sanitize() Christian Couder
2024-06-19 18:40 ` Eric Sunshine
2024-06-19 12:57 ` [PATCH 2/3] version: refactor get_uname_info() Christian Couder
2024-06-19 12:57 ` [PATCH 3/3] connect: advertise OS version Christian Couder
2024-06-19 13:18 ` [PATCH 0/3] Advertise " Dragan Simic
2024-06-19 13:45 ` Jeff King
2024-06-19 13:50 ` Dragan Simic
2024-06-19 14:01 ` Christian Couder
2024-06-19 14:19 ` Dragan Simic
2024-06-19 14:41 ` rsbecker
2024-06-19 14:52 ` Jeff King
2024-06-19 14:57 ` rsbecker
2024-06-19 15:53 ` Dragan Simic
2024-06-19 14:50 ` Jeff King
2024-06-19 15:25 ` rsbecker
2024-06-19 22:46 ` brian m. carlson
2024-06-20 15:25 ` Jeff King
2024-06-20 16:28 ` Junio C Hamano
2024-12-09 16:14 ` Usman Akinyemi
2024-12-09 16:34 ` rsbecker
2024-12-10 18:51 ` Usman Akinyemi [this message]
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=CAPSxiM8hYPAuZhiTX06jmw7FRr0_6P5+4WjudM9Ad84Lid6gDA@mail.gmail.com \
--to=usmanakinyemi202@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johncai86@gmail.com \
--cc=ps@pks.im \
--cc=rsbecker@nexbridge.com \
/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 NNTP newsgroup(s).