RE: git client enhancement request

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


I have to interject here that the git client doing a push must be fully
authenticated which implies to me that all the information required is
available to do so and allow the server repository to be updated.

Lionel B. Dyck <>< 
System Z Enthusiasts Discord:

?Worry more about your character than your reputation. Character is what you
are, reputation merely what others think you are.?   - - - John Wooden

-----Original Message-----
From: Junio C Hamano <gitster@xxxxxxxxx> 
Sent: Monday, May 13, 2024 1:51 PM
To: Sean Allred <allred.sean@xxxxxxxxx>
Cc: lbdyck@xxxxxxxxx; git@xxxxxxxxxxxxxxx
Subject: Re: git client enhancement request

Sean Allred <allred.sean@xxxxxxxxx> writes:

> Is this even technically feasible? My understanding is that storage 
> implementations of each forge vary *wildly*. I don't believe this 
> would be under Git's ability to implement as a project.

Not just "storage implementation", but some things are totally kept outside
the control of Git proper, including user and repository management.
Creating, deleting, and modifying authentication and authorization details
of these things are outside the scope of Git, and forges build on their
competing designs.

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux