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

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

From
Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
Date
Apr 19, 2010, 07:38 UTC
Message-ID
<v2me72faaa81004190038y4aeefa80g9f60bb3b1e795e4b@mail.gmail.com>
In-Reply-To
<7vfx2rsy6y.fsf@alter.siamese.dyndns.org>
On Mon, Apr 19, 2010 at 12:53 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 12 quoted lines
> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>
>> Pavan Kumar Sunkara <pavan.sss1991@gmail.com> writes:
>>
>>> Session management reduces the length of URL
>>
>> ... but OTOH, GET parameters allow painlessly cut-and-paste-able URLs,
>> which is in my opinion a must-have for gitweb.
>
> These self-contained URL are used in bookmarks and e-mails to the mailing
> list.  I think "the length of URL" is a red herring at best, and shortened
> URL that is not self-contained is not an advantage at all.
Yeah, I agree to that.
> 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.

So, why don't we do like this, There will be no need of session management when gitweb is installed in some site like repo.or.cz which needs copy'n'paste URLs but there will be session management when the write modules are enabled and when gitweb is installed locally or on intranet (basically when it is used to work on a repo).

What do you say ?
Show 7 quoted lines
> When I heard that somebody wants to do a "write support" in gitweb, I
> naturally thought the proposal was about implementing RFC3253 using git as
> a backend.  I think it would be a reasonable thing to do (as opposed to
> coming up with an ad-hoc "write support" mechanism that is not compatible
> with anybody else), but on the other hand it might be a bit too ambitious
> for a one-student summer project.
>

Sorry but I don't know what it is. The current average git used are in need of a git client and git-gui is not doing a good job of it. So, this proposal solves it by providing client features inside gitweb itself. :-)

-pavan
Previous: Junio C HamanoNext: Petr Baudis
Message 12 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.