git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sean Allred <allred.sean@gmail.com>
Cc: <lbdyck@gmail.com>,  <git@vger.kernel.org>
Subject: Re: git client enhancement request
Date: Mon, 13 May 2024 11:51:02 -0700	[thread overview]
Message-ID: <xmqq8r0dfsvd.fsf@gitster.g> (raw)
In-Reply-To: <m0pltptx3h.fsf@epic96565.epic.com> (Sean Allred's message of "Mon, 13 May 2024 12:56:02 -0500")

Sean Allred <allred.sean@gmail.com> 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.



  parent reply	other threads:[~2024-05-13 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 15:07 git client enhancement request lbdyck
2024-05-13 17:56 ` Sean Allred
2024-05-13 18:02   ` lbdyck
2024-05-13 18:51   ` Junio C Hamano [this message]
2024-05-13 19:00     ` lbdyck
2024-05-13 21:19       ` brian m. carlson
2024-05-13 19:09   ` rsbecker
2024-05-13 19:11     ` lbdyck

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=xmqq8r0dfsvd.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=allred.sean@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=lbdyck@gmail.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).