public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Khomoutov <kostix@bswap.ru>
To: git@vger.kernel.org
Subject: Re: Proposal and Validation of Git Compile
Date: Wed, 13 Mar 2024 12:59:16 +0300	[thread overview]
Message-ID: <20240313095916.ydcnyzhdmc6jbfms@carbon> (raw)
In-Reply-To: <CABCSMAeySCkg6A1R3PUwrHyWRKMKnBH3OGnd8OtX-OpsGoOTkQ@mail.gmail.com> <52ot6dibj4o5mhgsmxpa5r2hkllxrwwhf2azgkvtpaopldi2pg@5etkc4r3eunm>

On Tue, Mar 12, 2024 at 11:24:17PM -0400, Bhargav Vishnu wrote:

> I'm writing to propose and get a validation of one of the ideas I had for
> git tool.
[...]
> Eg: Code on a gist is copied into every repository, why not create and use
> the gist itself as it also has versioning?
[...]

In addition to what Reto said in their respective answer, you seem to confuse
Git (a version control tool) and Github - a turn-key Git hosting solution.
The thing is, the concept of "gists" does not exist in Git, and also it does
not have any real concept of a repository fork, a pull request, issue tracking
and so on.
That is, to build what you propose on your workflow picture, you'd need to
implement it in Github, not Git.

That said, I support what Reto said: Gists are merely pastebins [1] of the
21th century, and I think you perceive them as version-controlled code because
you supposedly are a relatively young person ;-) For an old fart like me,
Gists are just a sort of convenient way to share snippets of code with someone
else (say, when you're chatting on StackOverflow or elsewhere and would like
to show to your peer a bit more than a one-liner).

And if we think about making reusable pieces of code, this is ineed a solved
problem: libraries, packages and package repositories.
Not that I do not find your idea having a particular appeal - it does, - just
it's not in the domain of Git itself. A packaging system could possibly
somehow intergate with Gists (but note that that could only really sensibly
work for interpreted languages such as JS, which you seem to think of anyway),
but that's a task for that package system, not Git. For instance, Go's package
management system allows storage of the packages (in the form of the source
code) using multiple VC systems - namely, Git, Mercurial, Fossil and
Subversion, and it's semi-transparent to the users. Note that implementing
this package system did not require any support from the mentioned VC systems.
Quite possibly, say, NPM, could be made to work with Gists in the way you
envision, but it's to be discussed with NPM folks, not Git folks.

 1. https://en.wikipedia.org/wiki/Pastebin


      reply	other threads:[~2024-03-13  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13  3:24 Proposal and Validation of Git Compile Bhargav Vishnu
2024-03-13  8:08 ` Reto
2024-03-13  9:59   ` Konstantin Khomoutov [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=20240313095916.ydcnyzhdmc6jbfms@carbon \
    --to=kostix@bswap.ru \
    --cc=git@vger.kernel.org \
    /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