From: Eric Wong <e@80x24.org>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: workflows@vger.kernel.org, git@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: email as a bona fide git transport
Date: Fri, 18 Oct 2019 02:22:53 +0000 [thread overview]
Message-ID: <20191018022253.GA29290@dcvr> (raw)
In-Reply-To: <b9fb52b8-8168-6bf0-9a72-1e6c44a281a5@oracle.com>
Vegard Nossum <vegard.nossum@oracle.com> wrote:
<snip>
> Disadvantages:
>
> - requires patching git
The bigger disadvantage is this won't work with a historical
patch series (and some folks stay on ancient git). But maybe
that window for that is only a few years...
The toughest part right now for public-inbox is trying to make
sense of --range-diff (supporting --interdiff would be easy, I
think...). Also, we've only had --range-diff for a year or
so.
Your proposal would make things 100% easier for public-inbox
to deal with future --range-diff uses, however :)
> - requires a bot to continuously create branches for patchsets sent to
> mailing lists
Not necessarily, being able to search on commit OIDs would
be pretty handy itself for dealing with --range-diff output
in public-inbox, so there's no real need to actually make
the branch in git.
I also have a parallel solution in the works to make
--range-diff output more amenable for search engines like
public-inbox by adding blob OIDs to its output:
https://public-inbox.org/git/20191017121045.GA15364@dcvr/
I shall call myself an "SEO expert" from now on :>
> Thoughts?
Pretty much the same concerns others brought up around exactness
and working on top of cherry-picks.
> PS: Eric Wong described something that comes quite close to this idea, but
> AFAICT without actually recreating commits exactly. I've included the link
> for completeness. [4]
> [4]: https://lore.kernel.org/workflows/20191008003931.y4rc2dp64gbhv5ju@dcvr/
My plan is to work on interdiff support in the next week or so
once bugs are fixed and public-inbox v1.2 is out the door. Not
sure about range-diff and reverse-mapping blobs -> trees ->
commits, but searching on "git patch-id --stable" output is also
on the table.
PS: Attached patches: I have nothing against using MIME for those,
(not speaking for anybody else). public-inbox needs to handle
those better w.r.t search indexing linkification. And then
I found some bugs for --reindex corner cases which I'm still
working on :x
prev parent reply other threads:[~2019-10-18 6:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 10:22 email as a bona fide git transport Vegard Nossum
2019-10-16 11:10 ` Willy Tarreau
2019-10-16 14:45 ` Santiago Torres Arias
2019-10-17 20:43 ` Greg KH
2019-10-17 20:45 ` Konstantin Ryabitsev
2019-10-18 1:30 ` Greg KH
2019-10-18 1:54 ` Konstantin Ryabitsev
2019-10-18 2:52 ` Willy Tarreau
2019-10-18 6:34 ` Nicolas Belouin
2019-10-18 15:50 ` Santiago Torres Arias
2019-10-20 5:50 ` Laurent Pinchart
2019-10-18 14:27 ` Vegard Nossum
2019-10-18 15:54 ` Santiago Torres Arias
2019-10-18 16:03 ` Konstantin Ryabitsev
2019-10-18 16:11 ` Santiago Torres Arias
2019-10-18 18:00 ` Konstantin Ryabitsev
2019-10-18 16:15 ` Theodore Y. Ts'o
2019-10-18 16:50 ` Vegard Nossum
2019-10-18 19:14 ` Theodore Y. Ts'o
2019-10-20 3:17 ` Willy Tarreau
2019-10-20 6:28 ` Vegard Nossum
2019-10-22 12:11 ` Vegard Nossum
2019-10-22 13:53 ` Theodore Y. Ts'o
2019-10-22 16:29 ` Vegard Nossum
2019-10-22 19:01 ` Eric Wong
2019-10-16 15:00 ` Pratyush Yadav
2019-10-17 12:23 ` Vegard Nossum
2019-10-17 13:11 ` Theodore Y. Ts'o
2019-10-17 14:01 ` Vegard Nossum
2019-10-17 14:47 ` Theodore Y. Ts'o
2019-10-17 15:11 ` Steven Rostedt
2019-10-16 20:57 ` Jonathan Nieder
2019-10-17 13:08 ` Vegard Nossum
2019-10-17 3:17 ` Junio C Hamano
2019-10-17 13:30 ` Vegard Nossum
2019-10-18 2:22 ` Eric Wong [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=20191018022253.GA29290@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@oracle.com \
--cc=workflows@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.