One use-case I'd like this work to be able to address is:
Many of my colleagues don't want to use Git. If I send them a mail
with the cut-and-paste-ready "git clone" command, they'll still reply
asking for an attachment to an email, and they'll send me their
modifications the same way.
In a good write-enabled web interface, they'd browse the repository
online, pick a file, and the download page would point them to a URL
containing the filename, and the base commit, with a form to upload a
new version of the file.
Some time later, they could re-use the same URL, and upload the
modified version of the file. Actually, I could even do the first step
myself, and send them an email with the attachment and the URL, and
they'd upload their version whenever they want. The upload should
create a commit in a separate branch, starting from the base commit
contained in the URL. I could do the merge myself later in case of
non-fast forward.
That's a real senario, and I believe it would be a rather common
use-case of a web-based git client: a power-user prepares the work,
and sends well-prepared URL to newbies. This really requires GET
parameters.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
