[PATCH 2 of 3] changeset: adjust json output to use new/old (BC)

[Matt Mackall]

On Sat, 2016-04-16 at 14:40 +0900, Yuya Nishihara wrote:
> On Fri, 15 Apr 2016 13:00:11 -0400, timeless wrote:
> > 
> > On Fri, Apr 15, 2016 at 12:17 PM, Yuya Nishihara <yuya at tcha.org> wrote:
> > > 
> > > On Wed, 13 Apr 2016 12:14:35 -0500, timeless wrote:  
> > > > 
> > > > # HG changeset patch
> > > > # User timeless <timeless at mozdev.org>
> > > > # Date 1460548060 0
> > > > #      Wed Apr 13 11:47:40 2016 +0000
> > > > # Node ID 4161598737bc141a062d8fa0d2c90da823e5b6c9
> > > > # Parent  57f09cb9c2e69b0e8ef89cd21758722ba7e07ff6
> > > > changeset: adjust json output to use new/old (BC)
> > > > 
> > > > The previous json structure was not friendly to strongly structured
> > > > parsing.  
> > > Maybe I'm dumb, but I really can't understand what the "strongly
> > > structured
> > > parsing" is. Could you elaborate a little more?  
> > Basically being able to do : {object}.{well-known-property-name}
> > 
> > for a in copies:
> >    print(a.new.path, a.old.path)
> Hmm, it sounds like "I want this structure, so I made hg do that." It varies
> what structure is the best for users. The original structure is convenient
> to map new path to old path, for example.
> 
>   for p in files:
>       copies.get(p)

Right. It matches what hg does internally, which has proved convenient.

-- 
Mathematics is the supreme nostalgia of our time.