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

Re: Question re. git remote repository

From
MSMatt Seitz <mseitz@mhseitz.onmicrosoft.com>
Date
Jan 17, 2013, 05:20 UTC
Message-ID
<1BBEF94B6B46E54980290D150A6F2EDD46B718CB@BLUPRD0612MB625.namprd06.prod.outlook.com>
"David Lang" <david@lang.hm> wrote in message news:<alpine.DEB.2.02.1301161843390.21503@nftneq.ynat.uz>...
Show 10 quoted lines
> >>
> >> On Thu, 17 Jan 2013, Matt Seitz (matseitz) wrote:
> >>
> >>> 2. a repository where only one user does "git add" and "git commit",
> >> while other users will do "git pull", the peer-to-peer model (you pull changes
> >> from me, I pull changes from you).
> >>
> 
> you may _be_ safe, and if others who really know the internals speak up, take 
> their word on it. 
Well, we already have Linus's article.  I guess the question is whether the use case I describe above falls under:
A. "maintenance operations"
B. "normal git workflow"
Personally, I would consider this use case to be a "normal git workflow".
Message 1 of 1 in “Re: Question re. git remote repository”
  1. Matt SeitzJan 17, 2013

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.