[TERMINOLOGY] rename "changesets" to "revision bundles"

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Blackwell wrote:
> I'll betch you my nicest pair of shoes that a term like "bundle-revisions"
> would get get shortened to bundle before docs got written.
> 
> I hit the fridge (refrigerator) for a tv (television) dinner. I may be out
> and decide instead to get in the car (carriage, horseless carriage)/ auto
> (automobile). I'll then buy some gas (gasoline) on my way to hit the king
> (Burger king) for a burger (hamburger).

What's interesting to me is that we don't seem to have a
generally-accepted short form of "computer" yet.  I was betting on
"puter", but perhaps Strong Bad's "compy" will win the day.

> Kinda the same what that people seem to be calling shared repositories
> just repositories. I bet that eventually gets shortened even more to repo.

Absolutely.  Already has been (see the alias list for "init-repository").

But I think you're implying that we shouldn't use names that will be
shortened, and I don't think that's so.  Everyone knows that a tv is a
"television set", that a fridge is a "refrigerator".

In my dialect, "guest" and "guessed" have exactly the same pronunciation
(both end with a flap sound), but if you point that out to someone, they
will pronounce the words unnaturally to "prove" that they are different.
 When they do this, they're not merely slowing their speech, they're
making different final sounds (voiced and unvoiced stops), based on
their knowledge of the spelling of these words.

I think it's in the nature of human communication that we use ambiguous
forms whenever that is easy, and disambiguate only when context doesn't
resolve the ambiguities.

> My favorite would be ver/verset ("a set of 'viewable emailable
> revisions'").  Turn a set of revisions into a verset, and apply it to get
> a additioanal set of revisions back.  I also like revset. 

I'd prefer to use "revision" rather than "version", because that is what
is contained.  We may want to use "version" as something different from
"revision" in bzr, and equating them here would hinder that.  In the
software world, "version" often implies "release version", e.g. "version
1.0", "version 1.9", and so I think "version" is not a good replacement
for "revision".

"set" I can take or leave.  To me, "set" doesn't strongly imply that the
revisions have been joined together.  Though the similarity to
"changeset" might be an advantage.

I don't think calling them "revsets" will prevent shortening.  By
analogy with "changeset -> cset", they'd probably be called "rsets".

> I'll spare you any terms about portable containers. 

Aww.  And after you proposed "basket" for "repository"?

Given that they are directions from which "knits" or "weaves" are
produced, I'd have thought "pattern" would be a good analogy.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEewuY0F+nu1YWqI0RAhIwAJ9QdWo0MUAwLt4phb90pb7AjD/1tQCgh+I9
PA1PWdEdpwRwl3s3rbGl7yI=
=Mg15
-----END PGP SIGNATURE-----