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

Re: [RFC] Patches exchange is bad?

From
MCMarco Costalba <mcostalba@yahoo.it>
Date
Aug 18, 2005, 10:00 UTC
Message-ID
<20050818100023.80893.qmail@web26310.mail.ukl.yahoo.com>
Catalin Marinas wrote:
>
>The base of the StGIT stack in the HEAD repository (branch) should
>always be the head of the MAIN repository. 
That's the point I missed, now it's more clear.
Show 9 quoted lines
>
>That's how you would normally do development on Linux using StGIT -
>clone the mainline kernel, create patches in your StGIT tree and submit
>them either via e-mail or ask the gatekeeper to pull directly from your
>tree (assuming that you only push those patches that need to be merged).
>Doing a 'stg pull' would retrieve the latest changes from the mainline
>kernel (including the changes made by your patches which were merged
>upstream).
>

If I uderstand correctly you never commit patches from StGIT stack directly in your base git repository, in this example git HEAD, but you always round trip to MAIN.

Then you don't have two git repository: HEAD and MAIN

Infact there is only one git repository, MAIN, cloned on your box and called HEAD and with a StGIT stack added on top.

>
>Please let me know if this needs further clarification.
>

I think so. Please, reading my notes above tell me if I thinking right ;-)

Marco

__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Next: Catalin Marinas
Message 1 of 2 in “Re: [RFC] Patches exchange is bad?”
  1. Marco CostalbaAug 18, 2005
  2. Catalin MarinasAug 18, 2005

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.