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

Re: Tracking a branch using StGIT

From
Andy Whitcroft <apw@shadowen.org>
Date
Sep 15, 2006, 10:58 UTC
Message-ID
<450A8740.7000308@shadowen.org>
In-Reply-To
<b0943d9e0609150342y6105d8d1o61abb1934da9f51b@mail.gmail.com>
Catalin Marinas wrote:
Show 23 quoted lines
> On 15/09/06, Rajkumar S <rajkumars+git@gmail.com> wrote:
>> I am using StGIT to track a branch of a remote git repository
>> (actually a remote cvs repository, which I am tracking cvsimport)
> [...]
>> The .git/remotes/origin is
>> URL: /usr/local/pfSense/upstream/pfSense/.git
>> Pull: refs/heads/master:refs/heads/origin
>> Pull: refs/heads/avendor:refs/heads/avendor
>> Pull: refs/heads/Package-Reorg-2005:refs/heads/Package-Reorg-2005
>> Pull: refs/heads/RELENG_1:refs/heads/RELENG_1
>>
>> My requirement is to track RELENG_1 branch with StGIT while
>> maintaining my own patches. but when I do a stg pull the messages are:
> [...]
>> It seems StGIT is trying to merge the origin branch from remote to
>> RELENG_1 of local. Is there a way to get RELENG_1 of remote to merge
>> with MyBranch (clone of "RELENG_1") of local?
> 
> After StGIT pops all the patches, it just calls "git pull origin". My
> understanding of GIT is that this should update local RELENG_1 with
> the remote RELENG_1 from the "origin" repository. Anything wrong with
> my assumptions?
> 

Well that will update origin, and then merge the result with the current branch. That second part probabally isn't what you had in mind. Normally you would git fetch origin to stop that happening, but that also can't update the branch you are on.

Not sure if this helps.
-apw
Previous: Catalin MarinasNext: Santi
Message 3 of 10 in “Tracking a branch using StGIT”
  1. Rajkumar SSep 15, 2006
  2. Catalin MarinasSep 15, 2006
  3. Andy WhitcroftSep 15, 2006
  4. SantiSep 15, 2006
  5. Rajkumar SSep 15, 2006
  6. Rajkumar SSep 15, 2006
  7. Jakub NarebskiSep 15, 2006
  8. Rajkumar SSep 15, 2006
  9. Jakub NarebskiSep 15, 2006
  10. Rajkumar SSep 15, 2006

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.