On Mon, 03 Jul 2006, David Glasser wrote:
> On 7/3/06, Ben Collins-Sussman <email@example.com> wrote:
> >On 7/3/06, David Glasser <firstname.lastname@example.org> 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
> >> 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".
As with Mike, I very often -- ~60% of the time -- have multiple change
sets which overlap a single file. I would like to see the changelist
feature evolve (for files) to handle hunk or line number
identification within a single file. Using a more generic term like
"changelist" works well with that direction.
Received on Wed Jul 5 23:40:59 2006
- application/pgp-signature attachment: stored