From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 0CD1A208D0 for ; Wed, 16 Aug 2017 21:01:47 +0000 (UTC) Received: by mail-yw0-x22f.google.com with SMTP id s143so30196175ywg.1 for ; Wed, 16 Aug 2017 14:01:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=hOLj2ylB9kVpTClw4eZdLRd6T0Xw46u3E53a+kzSHEM=; b=olN+Q5xOEZbOAHeGZaLimJSh2q2l0hbVUO+uUo5i0FNRfQCzr3OFxhTmMAIO3gS+Ea 2m2tLZiu2pdFWd5so7tEDYFkKoybvNLrziq6vM45AXNdl61IG+CxoBPIJRZqc+GjbxK9 aHv5I7Qk0Xx0rohgo0Qqgx0oj9l5p4mm8TZ5oxBg/w6dxDwCwF8rzi5Y5oc52SpxfRj6 Q1Ej453yWimJsjgjV3MPk1SI6OVDveFv3X+XQNLntF3pXETsYWvlsEEKqIiuDuEWACme x/6i3+aq+XbF2DneexvWwdoVxEtdljLLEAHjrghNpUZF9uHfN62yA60TtCgYV+8S1aUK cBgA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=hOLj2ylB9kVpTClw4eZdLRd6T0Xw46u3E53a+kzSHEM=; b=OuVUBPU7hru10ltmF900H612TluUohBxhUtyWYDzf+3JKdwt6pkKXWe3fplfukSs06 6fNk0WWldRxQ3+9Ybq6R6U0lLQP+XbkSmxk44Ri+q3uvQrcvGxGPjge1iIV/GtmrzHMA Q+UA9A8ygNdVHSqkw7QKj+xjHn5agFnBi3ExNlM8fKZcucjUiJ75IB3NphMFtKMW9ys0 PTvOZPmaXFXI3xyRj4++jqQhVT64PRYbidaoqNm4j2P9sdHAlnmyMUu6NO3gHUmTYHhK /R3wv92l06FT4+pSEzxE1jfYd3wHRAnBirgKmbn8MigoIr5c0kRxtgd1oR4mxS34cUnF 3Yxg== X-Gm-Message-State: AHYfb5iz0I8prS/4Kiv19FDmZ4gNs03uli9a0+eLYVSsUrV9czCsDzW/ sP67/QwF6ffKk76JoarQCKviEX9YErdT X-Received: by 10.13.206.132 with SMTP id q126mr2375558ywd.337.1502917305679; Wed, 16 Aug 2017 14:01:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.56.142 with HTTP; Wed, 16 Aug 2017 14:01:45 -0700 (PDT) From: Stefan Beller Date: Wed, 16 Aug 2017 14:01:45 -0700 Message-ID: Subject: Nonlinear history? To: Eric Wong , meta@public-inbox.org Content-Type: text/plain; charset="UTF-8" List-Id: So I happened to search an old post of mine today, specifically I knew only a couple of bits of it: * I authored a patch series, that had a given string in the name ("protocolv2") * I was looking for an answer by Peff To find the post in question I used both the local git mailing list repository (as cloned from https://public-inbox.org/git) to find the starting point[1] as well as the online list to see the relations between posts, such that I finally arrived at [2]. However in the process of searching locally I wondered if the repository data could be organized better, instead of linearly. So what if the git history would reflect the parent relationships of the emails? Essentially each email is comparable to a topic branch in the git workflow (potentially with other series/email on top of it). Each topic would be merged to master immediately, such that the first parent master branch history consists of merges only; the second parent is the new ingested email, which is either a root-commit (when a new topic is started), or a commit building on top of another commit (which contains the email it is responding to; that other commit is merged to master already). Has this idea been come up before or even discussed before? Thanks, Stefan [1] I really like the search by author feature! [2] https://public-inbox.org/git/20150604130902.GA12404@peff.net/