Hi,

With old CVS the curl-commits mailing served a couple of purposes, it
was easy to view which changes were taking place in the repo, and it
was very easy to 'replay' lost commits that had taken place between
server backup and server crash.

With current git configuration curl-commits mails do not include
diffs, they include a link to the repo. If the repo for any reason
gets corrupted these mails serve no purpose. Is if possible to have
true diffs included in curl-commits mails?

Another thing I miss with git, even without having started to use it,
is that with git, files have no revision Id or number. It may be a git
philosophical thing, no matter what this version control system
thinks, content is provided in files and files have a history and as
such a revision number.

Having to update revision number by hand is plain nonsense. There are
times when one or many people work with files that come out of a repo
and that are moved to other machines where there is no version control
installed. Ensuring that everyone starts to work with the same initial
document becomes a nightmare. And don't tell me that everyone in the
team must know how to use git because that won't happen in a million
years. Not everyone in the team is a developer, not all content is
source code, and only a fraction of the team knows what a version
control system is.

Another thing that shows that git is yet in its infancy is the use of
internal keys as external references. GUID's are fine as primary keys
in a database, but only for internal purposes. Exposing these as the
primary way of identifying elements, no matter if these are code
commits, financial transactions or cake recipes makes little sense,
except maybe for debugging purposes.

-- 
-=[Yang]=-
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html