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

Re: Git & Project Workflow

From
NSNicolas Sebrecht <nicolas.s.dev@gmx.fr>
Date
Nov 6, 2009, 21:44 UTC
Message-ID
<20091106214452.GA13724@vidovic>
In-Reply-To
<ae09c2a40911051619s36c9a781pdb403fb9140affdf@mail.gmail.com>
The 05/11/09, Tommy Wang wrote:
> Hi,
Hi,
>      it takes considerably more time to look through a list of
> commits, and pick out the ones that can be moved from main -> limited.

Instead of doing this massive (time consuming) cherry-picking, why don't you avoid the whole "main -> limited" workflow ? This looks a bit ugly for me.

I think that the main developers should work by default with the limited repo and only commit for the secret files into main. This would result in only pulling limited work into main ("limited -> main" workflow).

Let's rename main to secret and limited to normal to have the semantic stick with my point. In this case, whole developers work with normal for the "normal" tasks. If they need a secret change, secret developers commit and push to secret. Then, you only need to pull normal from secret and resolve conflicts in one place.

-- 
Nicolas Sebrecht
Previous: Tommy Wang
Message 2 of 2 in “Git & Project Workflow”
  1. Tommy WangNov 6, 2009
  2. Nicolas SebrechtNov 6, 2009

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.