
---

! Notes on `what-changed' Output

Here are the starting points for fixing `what-changed'.

---

<<<

From: Robert W Anderson <rwa@alumni.princeton.edu>
Subject: [arch-users] Re: [arch-dev] per-file changes, what-changed useability (was Emacs
 mode and tutorial)
Date: Thu, 11 Apr 2002 07:58:52 -0700

>
>
>
>Per-file changes is a must-have feature for arch, IMHO.
>
Agreed.

I also find the output of what-changed to be a useability regression 
compared to 'cvs -nq upd'.
The output is a real estate hog, and I haven't been able to figure out 
how to keep what-changed
from leaving around those ,,* dirs which I never use.

I would prefer the cvs style of organizing the output by file with a 
status code, rather than by category of change with a list of files, or 
<none>.  That's backwards from what I care about.

Bob

>
>_______________________________________________
>arch-dev mailing list
>arch-dev@regexps.com
>http://www.regexps.com/mailman/listinfo/arch-dev
>



_______________________________________________
arch-users mailing list
arch-users@regexps.com
http://www.regexps.com/mailman/listinfo/arch-users




>>>

---


<<<

From: Adam Spiers <arch-users@adamspiers.org>
Subject: Re: [arch-users] Re: [arch-dev] per-file changes, what-changed useability (was Emacs mode and tutorial)
Date: Thu, 11 Apr 2002 16:05:37 +0100

Robert W Anderson (rwa@alumni.princeton.edu) wrote:
> I would prefer the cvs style of organizing the [what-changed] output
> by file with a status code, rather than by category of change with a
> list of files, or <none>.  That's backwards from what I care about.

Me too.  If you've modified two files, foo1/bar1/baz1 and
foo2/bar2/baz2, and added a new file foo1/bar1/baz2, it's more likely
that the modification of foo1/bar1/baz is related to the addition of
foo1/bar1/baz2 than it is to the modification of foo2/bar2/baz2, since
it's in the same directory.  Therefore it makes more sense to sort by
path name.
_______________________________________________
arch-users mailing list
arch-users@regexps.com
http://www.regexps.com/mailman/listinfo/arch-users



>>>

---

<<<


From: Karel Gardas <kgardas@objectsecurity.com>
Subject: Re: [arch-users] Re: [arch-dev] per-file changes, what-changed
 useability
Date: Fri, 12 Apr 2002 22:31:54 +0200 (CEST)

On Fri, 12 Apr 2002, Walter Landry wrote:

> > In any case, the output is just far too verbose.  If nothing changed, I
> > want no output.
>
> I would have been able to give you a quick and dirty script to do
> that, but the return values for larch what-changed are not quite what
> I would expect.
>

Oh, you are rewritting this behaviour? Can I describe my idea about larch
(cvs-like) output? I hope so :-) Simply I prefer file per line status as
in cvs command line client and it'll be easy to parse it for later usage
in gui-based clients.

Example:

larch whats-missing
patch-20
patch-21

larch whats-missing --files
patch-20
A mico/orb/thread.cc
A mico/include/mico/thread.h
patch-21
R mico/orb/Operation.cc -> mico/orb/operation.cc
P mico/orb/Makefile

where 'A' is added
      'R' is removed or moved to
      'P' is patched

I hope that command 'what-changed' can have similar output except patches
names.

What do you think about it?

Karel
--
Karel Gardas                  kgardas@objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com

_______________________________________________
arch-users mailing list
arch-users@regexps.com
http://www.regexps.com/mailman/listinfo/arch-users


>>>


%%% tag: Tom Lord Wed May  1 23:20:16 2002 (ArchRevCtl.d/WhatChangedOutput)
%%%

