git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: GSoC 2010: "Integrated Web Client for git" proposal

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Apr 19, 2010, 12:27 UTC
Message-ID
<vpq8w8j1vb7.fsf@bauges.imag.fr>
In-Reply-To
<20100419090734.GA10939@machine.or.cz>
Petr Baudis <pasky@suse.cz> writes:
Show 11 quoted lines
> On Mon, Apr 19, 2010 at 01:08:26PM +0530, Pavan Kumar Sunkara wrote:
>> On Mon, Apr 19, 2010 at 12:53 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> > On the other hand, a proposal about giving multiple clients access to
>> > their own individual server-side checkouts (ala "workspace" in DELTA-V)
>> > would require some mechanism to maintain the state on the server end, and
>> > session management would be one ingredient necessary to achieve that.
>
> But what if I will want to give a link to my "workspace" to someone
> else? You can embed workspace id in the URL, in fact you would probably
> just use it instead of project name completely naturally. I still don't
> see any need for sessions.
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/
Previous: Petr BaudisNext: Pavan Kumar Sunkara
Message 14 of 39 in “GSoC 2010: "Integrated Web Client for git" proposal”
  1. Christian CouderApr 15, 2010
  2. Jakub NarebskiApr 18, 2010
  3. Petr BaudisApr 18, 2010
  4. Jakub NarebskiApr 18, 2010
  5. Petr BaudisApr 18, 2010
  6. Pavan Kumar SunkaraApr 18, 2010
  7. Jakub NarebskiApr 18, 2010
  8. Petr BaudisApr 18, 2010
  9. Pavan Kumar SunkaraApr 19, 2010
  10. Matthieu MoyApr 19, 2010
  11. Junio C HamanoApr 19, 2010
  12. Pavan Kumar SunkaraApr 19, 2010
  13. Petr BaudisApr 19, 2010
  14. Matthieu MoyApr 19, 2010
  15. Pavan Kumar SunkaraApr 19, 2010
  16. Matthieu MoyApr 19, 2010
  17. Petr BaudisApr 19, 2010
  18. Pavan Kumar SunkaraApr 19, 2010
  19. Petr BaudisApr 20, 2010
  20. Jakub NarebskiApr 18, 2010
  21. Petr BaudisApr 18, 2010
  22. Jakub NarebskiApr 19, 2010
  23. Petr BaudisApr 19, 2010
  24. Pavan Kumar SunkaraApr 19, 2010
  25. Petr BaudisApr 20, 2010
  26. Jakub NarebskiApr 20, 2010
  27. Pavan Kumar SunkaraApr 21, 2010
  28. Petr BaudisApr 22, 2010
  29. Junio C HamanoApr 22, 2010
  30. Petr BaudisApr 23, 2010
  31. Junio C HamanoApr 23, 2010
  32. Pavan Kumar SunkaraApr 22, 2010
  33. Christian CouderApr 23, 2010
  34. Pavan Kumar SunkaraApr 23, 2010
  35. Pavan Kumar SunkaraApr 19, 2010
  36. Jakub NarebskiApr 19, 2010
  37. Pavan Kumar SunkaraApr 19, 2010
  38. Jakub NarebskiApr 19, 2010
  39. Pavan Kumar SunkaraApr 20, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.