From: Sebastian Schuberth <sschuberth@gmail.com>
To: Eric Wong <e@80x24.org>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
patchwork@lists.ozlabs.org
Subject: Re: Pain points in Git's patch flow
Date: Mon, 19 Apr 2021 21:49:46 +0200 [thread overview]
Message-ID: <CAHGBnuOv5PvCcKqed-sTOs2uxyuhRS7RDF4XvzPu9oHpyroasQ@mail.gmail.com> (raw)
In-Reply-To: <20210419193600.GA19186@dcvr>
On Mon, Apr 19, 2021 at 9:36 PM Eric Wong <e@80x24.org> wrote:
> > Also, I wouldn't say I "gave up in frustration". It was a mostly
> > unemotional decision on which of the many OSS projects I contribute to
> > my rare spare time is spent best.
>
> I guess some things aren't for everybody. When I started
> git-svn, I never expected git to be the right tool for others.
> I figured most folks could just continue using SVN since they
> seem to like centralized things or at least have some sort of
> "authority" to look to.
>
> I'm largely uninvolved with git nowadays since I'm reasonably
> satisfied with how it works; that and I prefer scripting
> languages rather than ahead-of-time languages.
True, since quite a while I'm also at a point where I'm satisfied with
how Git (for Windows) works, so I also ceased to see the need to
contribute. That's indeed another reason I forgot to mention.
> To watch a particular filename, the "dfn:" prefix may be used.
> The prefixes supported for a particular instance are documented in
> <https://public-inbox.org/git/_/text/help/>, and you
> can watch multiple files by combining with "OR".
Thanks for pointing out these interesting features, I wasn't aware of them.
> I don't think any sort of radicle "flag day" or tool mandate is
> going to fly. I seem to recall at least one prominent Linux
> kernel hacker doesn't even use git; though I'm not sure if
> that's still the case.
Like you said in the beginning, I guess some things aren't for everybody.
> Email is already well-established with a good amount of small
> players, and plain-text is relatively inexpensive. So it seems
> best to build off the only halfway-decentralized thing we have
> in wide use, rather than trying to start from scratch.
While I can understand that conservative approach for a community
around a tool as important as Git, I still fear that only ever
sticking to technology that is already in wide use will hinder to look
over the rim of the tea cup.
--
Sebastian Schuberth
next prev parent reply other threads:[~2021-04-19 19:50 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 6:13 Pain points in Git's patch flow Jonathan Nieder
2021-04-14 7:22 ` Bagas Sanjaya
2021-04-14 8:02 ` Junio C Hamano
2021-04-14 21:42 ` Junio C Hamano
2021-04-15 8:49 ` Denton Liu
2021-04-15 6:06 ` Junio C Hamano
2021-04-15 15:45 ` Son Luong Ngoc
2021-04-19 2:57 ` Eric Wong
2021-04-19 13:35 ` Theodore Ts'o
2021-04-21 10:19 ` Ævar Arnfjörð Bjarmason
2021-04-28 7:21 ` Eric Wong
2021-04-28 7:05 ` Eric Wong
2021-04-15 18:25 ` Atharva Raykar
2021-04-16 19:50 ` Junio C Hamano
2021-04-16 20:25 ` Junio C Hamano
2021-05-02 5:35 ` ZheNing Hu
2021-04-18 8:29 ` Sebastian Schuberth
2021-04-18 20:54 ` Ævar Arnfjörð Bjarmason
2021-04-19 2:58 ` Eric Wong
2021-04-19 5:54 ` Sebastian Schuberth
2021-04-19 6:04 ` Sebastian Schuberth
2021-04-19 8:26 ` Ævar Arnfjörð Bjarmason
2021-04-19 19:23 ` Sebastian Schuberth
2021-04-19 22:34 ` Theodore Ts'o
2021-04-20 6:30 ` Sebastian Schuberth
2021-04-20 16:37 ` Theodore Ts'o
2021-04-30 20:45 ` Felipe Contreras
2021-04-20 10:34 ` Ævar Arnfjörð Bjarmason
2021-04-19 19:36 ` Eric Wong
2021-04-19 19:49 ` Sebastian Schuberth [this message]
2021-04-19 22:00 ` Konstantin Ryabitsev
2021-05-08 2:10 ` dwh
2021-04-19 21:49 ` Konstantin Ryabitsev
2021-04-19 23:03 ` Stephen Smith
2021-05-08 2:08 ` dwh
2021-05-08 4:41 ` Bagas Sanjaya
2021-04-30 20:58 ` Felipe Contreras
2021-04-21 4:46 ` Daniel Axtens
2021-04-26 2:04 ` brian m. carlson
2021-04-26 14:24 ` Theodore Ts'o
2021-04-26 14:36 ` Ævar Arnfjörð Bjarmason
2021-04-28 7:59 ` Eric Wong
2021-04-28 22:44 ` brian m. carlson
2021-04-30 20:16 ` Felipe Contreras
2021-04-30 20:35 ` Felipe Contreras
2021-04-30 21:09 ` Felipe Contreras
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHGBnuOv5PvCcKqed-sTOs2uxyuhRS7RDF4XvzPu9oHpyroasQ@mail.gmail.com \
--to=sschuberth@gmail.com \
--cc=avarab@gmail.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=patchwork@lists.ozlabs.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).