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

RE: [PATCH] branch: make -v useful

From
KRKerry, Richard <richard.kerry@atos.net>
Date
Jun 8, 2021, 11:32 UTC
Message-ID
<AS8PR02MB7302955796AAEF8B9063505E9C379@AS8PR02MB7302.eurprd02.prod.outlook.com>
In-Reply-To
<60bf36f24d2e2_1a848720836@natae.notmuch>
-----Original Message-----
From: Felipe Contreras <felipe.contreras@gmail.com> 
Sent: 08 June 2021 10:23
To: Kerry, Richard <richard.kerry@atos.net>; Felipe Contreras <felipe.contreras@gmail.com>; Jeff King <peff@peff.net>
Cc: Ævar Arnfjörð Bjarmason <avarab@gmail.com>; git@vger.kernel.org; Junio C Hamano <gitster@pobox.com>
Subject: RE: [PATCH] branch: make -v useful
Caution! External email. Do not open attachments or click links, unless this email comes from a known sender and you know the content is safe.
Kerry, Richard wrote:
Show 7 quoted lines
> 
>  > Git is a distributed VCS, most people don't have commit access to  
> > the original repository, therefore they push to their personal  > 
> repository (e.g. github fork).
> 
> [RK] When you say "most people", do you mean "most people who are 
> working on open source projects"?
Both.
Two-way workflows are present both in open source projects and private projects.
Triangular workflows are present both in open source projects and private project.
> [RK] I'm working using Git every day, and I pull from the original 
> repository and push back to it. I am working on closed source company 
> projects.
The triangularity I'm referring to is not per repository, it's per branch.

Do you always push to the same remote branch you pull from? [RK] Yes. There are two people doing most of the work , me and one other. We each mostly: [RK] 1. Are not working on the same things. Ie we don't generate many conflicts [RK] 2. Pull and push to the same branch. Ie each of us has a branch that we work on. He uses "master", I have my own (It is a single very long-lived branch - I know that isn't a recommended workflow but that's where we are for the moment)

How about rebasing or merging? Do you use the same remote branch? [RK] Merges are infrequent, but because we are working in different areas, we merge to "our own" branch (few conflicts, usually) and push to its remote. [RK] I have never yet done a rebase, but need to do so soon as there is work in an area that we have both worked on. Then it will be pushed to the usual place - ie the two branches mentioned above.

[RK] So basically, no, not triangular at all, if I understand the meaning of triangular (pull and push to different remotes).
Cheers.

-- Felipe Contreras

Previous: Felipe ContrerasNext: Felipe Contreras
Message 11 of 18 in “branch: make -v useful”
  1. branch: make -v usefulFelipe Contreras, Jun 5, 2021
  2. Ævar Arnfjörð BjarmasonJun 5, 2021
  3. Jeff KingJun 5, 2021
  4. Felipe ContrerasJun 7, 2021
  5. Jeff KingJun 8, 2021
  6. Felipe ContrerasJun 8, 2021
  7. Jeff KingJun 8, 2021
  8. Felipe ContrerasJun 8, 2021
  9. Kerry, RichardJun 8, 2021
  10. Felipe ContrerasJun 8, 2021
  11. Kerry, RichardJun 8, 2021
  12. Felipe ContrerasJun 10, 2021
  13. Kerry, RichardJun 25, 2021
  14. Felipe ContrerasJun 25, 2021
  15. Felipe ContrerasJun 7, 2021
  16. Ævar Arnfjörð BjarmasonJun 7, 2021
  17. Felipe ContrerasJun 7, 2021
  18. Felipe ContrerasJun 7, 2021

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.