Re: [Monotone-devel] Re: How to find out author of a code fragment?

[Nathaniel Smith]

On Wed, May 16, 2007 at 03:55:36PM +0100, Bruce Stephens wrote:
> Maybe a reverse-annotate, which looks at history backwards, showing
> which lines in the earliest lasted until which revision?  Or maybe
> that's just silly, and wouldn't be worth the effort.  Probably better
> just to have a way to get annotate to show removed lines.

Oh, I know: how about an 'annotate diff' combination command, that
shows a unidiff, but also marks each + and - line with the person
responsible for that change?

Doesn't help if you are looking at a file and wondering generally how
it came to look the way it does, very very cool if you know that
something has appeared or disappeared (and thus have some reference
point), and want to know what happened.

$ mtn annodiff -r t:monotone-0.26 -r t:monotone-0.27
[...]
         --- xdelta.hh
         +++ xdelta.hh
         @@ -38,5 +42,16 @@ u64 measure_delta_target_size(std::strin
 
          u64 measure_delta_target_size(std::string const & delta);
graydon: +void invert_xdelta(std::string const & old_str,
graydon: +                  std::string const & delta,
graydon: +                  std::string & delta_inverse);
 
    njs: +// Local Variables:
    njs: +// mode: C++
    njs: +// fill-column: 76
    njs: +// c-file-style: "gnu"
    njs: +// indent-tabs-mode: nil
    njs: +// End:
    njs: +// vim: 
et:sw=2:sts=2:ts=2:cino=>2s,{s,\:s,+s,t0,g0,^-2,e-2,n-2,p2s,(0,=s:
    njs: +
         #endif // __XDELTA_HH__

-- Nathaniel

-- 
The Universe may  /  Be as large as they say
But it wouldn't be missed  /  If it didn't exist.
  -- Piet Hein