Excerpts from Jun Wu's message of 2017-07-13 08:42:11 -0700:
> Excerpts from Boris Feld's message of 2017-07-13 12:32:39 +0200:
> > I think there was a misunderstanding about obsfate that I will try to
> > clarify, this email is a bit long, sorry.
> >
> > TL;DR:
> > - hg log is a
Excerpts from Boris Feld's message of 2017-07-13 12:32:39 +0200:
> I think there was a misunderstanding about obsfate that I will try to
> clarify, this email is a bit long, sorry.
>
> TL;DR:
> - hg log is a changeset-centric command
> - obsfate template summarize the obs-history between a
I think there was a misunderstanding about obsfate that I will try to
clarify, this email is a bit long, sorry.
TL;DR:
- hg log is a changeset-centric command
- obsfate template summarize the obs-history between a changeset and
its successors, history that can span several obs-markers
- hg obslog
As previously discussed in the "operation" thread [1]. I think we want to
use "operation" metadata instead of introducing flags, "obsfate" and/or
"verb" as new concepts. Practically "rebased as X" / "histedited as X" is
more friendly to end-user than just "rewritten as X".
With "operation"
On Wed, 12 Jul 2017 15:44:13 +0200, Boris Feld wrote:
> On Wed, 2017-07-12 at 00:06 +0900, Yuya Nishihara wrote:
> > Guessing from the PATCH 4, which has the following functions,
> >
> > obsfatedata: ctx => [succs, ...] => [(succs, markers), ...]
> >
> > maybe we'll want a template function
On Wed, 2017-07-12 at 00:06 +0900, Yuya Nishihara wrote:
> On Tue, 11 Jul 2017 11:16:03 +0200, Boris Feld wrote:
> > Obsfate has a difficult task: summarize the obsolescence history
> > (potentially spanning multiple obs-markers), aggregating the
> > different
> > values and all of this in
On Tue, 11 Jul 2017 12:44:52 -0700, Jun Wu wrote:
> Excerpts from Yuya Nishihara's message of 2017-07-12 00:06:13 +0900:
> > Well, I don't have expertise in the obsolete thingy, though I'm
> > (unfortunately)
> > a template expert.
> >
> > Guessing from the PATCH 4, which has the following
Excerpts from Yuya Nishihara's message of 2017-07-12 00:06:13 +0900:
> Well, I don't have expertise in the obsolete thingy, though I'm
> (unfortunately)
> a template expert.
>
> Guessing from the PATCH 4, which has the following functions,
>
> obsfatedata: ctx => [succs, ...] => [(succs,
On Tue, 11 Jul 2017 11:16:03 +0200, Boris Feld wrote:
> Obsfate has a difficult task: summarize the obsolescence history
> (potentially spanning multiple obs-markers), aggregating the different
> values and all of this in multiple dimensions when there's a
> divergence.
>
> This template seems
On Fri, 2017-07-07 at 21:09 +0900, Yuya Nishihara wrote:
> On Thu, 06 Jul 2017 23:50:17 +0200, Boris Feld wrote:
> > # HG changeset patch
> > # User Boris Feld
> > # Date 1499085172 -7200
> > # Mon Jul 03 14:32:52 2017 +0200
> > # Node ID
On Thu, 2017-07-06 at 18:05 -0700, Sean Farley wrote:
> Boris Feld writes:
>
> > # HG changeset patch
> > # User Boris Feld
> > # Date 1499085172 -7200
> > # Mon Jul 03 14:32:52 2017 +0200
> > # Node ID
Boris Feld writes:
> # HG changeset patch
> # User Boris Feld
> # Date 1499085172 -7200
> # Mon Jul 03 14:32:52 2017 +0200
> # Node ID e18d8e61b7260e246a82727c8cde01f936692cff
> # Parent 098585d4fbc88dc54513e12fa306d0e52ea2b323
> #
# HG changeset patch
# User Boris Feld
# Date 1499085172 -7200
# Mon Jul 03 14:32:52 2017 +0200
# Node ID e18d8e61b7260e246a82727c8cde01f936692cff
# Parent 098585d4fbc88dc54513e12fa306d0e52ea2b323
# EXP-Topic obsfatetemplate
template: use template-engine for obsfate
13 matches
Mail list logo