Re: Merge info display

2011-10-05 Thread Johan Corveleyn
On Wed, Oct 5, 2011 at 5:37 AM, Branko Čibej wrote: > On 30.09.2011 16:03, Julian Foad wrote: >> On Fri, 2011-09-30 at 17:27 +0400, Ivan Zhakov wrote: >>> On Fri, Sep 30, 2011 at 17:20, Johan Corveleyn wrote: >>> Yes, please keep the old output (one rev per line) available somehow. I ha

Re: Merge info display

2011-10-04 Thread Branko Čibej
On 30.09.2011 16:03, Julian Foad wrote: > On Fri, 2011-09-30 at 17:27 +0400, Ivan Zhakov wrote: >> On Fri, Sep 30, 2011 at 17:20, Johan Corveleyn wrote: >> >>> Yes, please keep the old output (one rev per line) available somehow. >>> I have developed quite a lot of scripts in our company that use

Re: Merge info display

2011-10-04 Thread Julian Foad
On Fri, 2011-09-30, Paul Burba wrote: > So as to keep my thoughts on the medium of record, I'm pasting my > comments on your doc here, rather than as comments in google docs : Thanks for all your comments, Paul. > (Which raises a question, why aren't we keeping these notes in our own > repository

Re: Merge info display

2011-09-30 Thread Paul Burba
On Fri, Sep 30, 2011 at 7:24 AM, Julian Foad wrote: > I've been thinking about a bunch of issues related to merging and how to > help users to avoid some of the common pitfalls.  One subset of my > thoughts is on how we can present information about merges in a more > user-friendly high-level way

Re: Merge info display

2011-09-30 Thread Julian Foad
On Fri, 2011-09-30 at 14:42 +0200, Stefan Sperling wrote: > On Fri, Sep 30, 2011 at 12:24:04PM +0100, Julian Foad wrote: > > I've been thinking about a bunch of issues related to merging and how to > > help users to avoid some of the common pitfalls. One subset of my > > thoughts is on how we can

Re: Merge info display

2011-09-30 Thread Julian Foad
I (Julian Foad) wrote: > I'm writing down my thoughts in this public document > ; > see especially under the "Reporting ..." section headings. Apparently that wasn't publicly visible. So

Re: Merge info display

2011-09-30 Thread Julian Foad
On Fri, 2011-09-30 at 17:27 +0400, Ivan Zhakov wrote: > On Fri, Sep 30, 2011 at 17:20, Johan Corveleyn wrote: > > On Fri, Sep 30, 2011 at 2:42 PM, Stefan Sperling wrote: > >> In principle, we should keep the current output by default (for backwards > >> compat), and add a new switch that enables

Re: Merge info display

2011-09-30 Thread Ivan Zhakov
On Fri, Sep 30, 2011 at 17:20, Johan Corveleyn wrote: > On Fri, Sep 30, 2011 at 2:42 PM, Stefan Sperling wrote: >> On Fri, Sep 30, 2011 at 12:24:04PM +0100, Julian Foad wrote: >>> I've been thinking about a bunch of issues related to merging and how to >>> help users to avoid some of the common p

Re: Merge info display

2011-09-30 Thread Johan Corveleyn
On Fri, Sep 30, 2011 at 2:42 PM, Stefan Sperling wrote: > On Fri, Sep 30, 2011 at 12:24:04PM +0100, Julian Foad wrote: >> I've been thinking about a bunch of issues related to merging and how to >> help users to avoid some of the common pitfalls.  One subset of my >> thoughts is on how we can pres

Re: Merge info display

2011-09-30 Thread Stefan Sperling
On Fri, Sep 30, 2011 at 12:24:04PM +0100, Julian Foad wrote: > I've been thinking about a bunch of issues related to merging and how to > help users to avoid some of the common pitfalls. One subset of my > thoughts is on how we can present information about merges in a more > user-friendly high-le