Re: changelist feature in trunk, for toying with

On 7/3/06, Ben Collins-Sussman <sussman@red-bean.com> wrote:
> On 7/3/06, David Glasser <glasser@mit.edu> wrote:
> > Specifically, the changelist (in the currently proposed/implemented design) is
> > fundamentally *not* a list of changes: it's a list of files. The name "change
> > list" implies to me that it applies at the level of individual hunk changes, not
> > at the file-level granularity.
>
> That would be a 'patch', right? A collection of hunk changes? :-)

Heh. The point I was trying to make is that you (with good reason)
aren't worrying about dealing with "overlapping changelists", which is
easier to understand if the feature is called something like "path
list" instead of "changelist".

> It's not just a list of files, it's a list of paths. Paths can be
> files or dirs.

Good point.

> I think the reason we've latched onto the term 'changelist' here is
> because we're picking up the word from perforce. In fact, we're flat
> out copying a lot of this idea from perforce, so we're trying to keep
> momentum with the huge number of perforce users out there.
>
> Take a look at the designdoc in notes/. Does it make things clearer?

Right; I understand that developers coming from Perforce are probably
looking for this feature under the name of changelist. I just wanted
to get the idea out there that folks *not* coming from Perforce might
find the name to be strange. If nobody else thinks the same thing as
me, then that's a moot point though :)

--dave

-- 
David Glasser | glasser@mit.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org