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

Re: Git Vs. Svn for a project which *must* distribute binaries too.

From
Bryan Childs <godeater@gmail.com>
Date
Jun 7, 2007, 07:57 UTC
Message-ID
<5971b1ba0706070057l2d4b170emd8af733d888d6a56@mail.gmail.com>
In-Reply-To
<20070607043632.31891.qmail@science.horizon.com>
On 7 Jun 2007 00:36:32 -0400, linux@horizon.com <linux@horizon.com> wrote:
> There's no reason that git can't do everything you have svn doing.
> What SVN calls "commit access" is what git refers to as "push access",
> but it's exactly the same thing.  I don't see how it's the tiniest bit
> more difficult.
<snip>

Thanks for this extremely length and informative reply - it's answered all our concerns, and we may well move to git sooner rather than later now!

Bryan
Previous: linux@horizon.comNext: linux@horizon.com
Message 2 of 4 in “Re: Git Vs. Svn for a project which *must* distribute binaries too.”
  1. linux@horizon.comJun 7, 2007
  2. Bryan ChildsJun 7, 2007
  3. linux@horizon.comJun 7, 2007
  4. Jan HudecJun 8, 2007

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.