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

Re: Cloning an StGit repository

From
Karl Hasselström <kha@treskal.com>
Date
Oct 18, 2007, 12:51 UTC
Message-ID
<20071018125132.GA5403@diana.vm.bytemark.co.uk>
In-Reply-To
<64de5c8b0710180456x24031754od7062d504e72b215@mail.gmail.com>
On 2007-10-18 17:26:48 +0530, Rajkumar S wrote:
> git --bare fetch ../stg_branch my_branch02:my_branch02
> my_branch02:my_branch02 my_branch01:my_branch01  master:master
[...]
Show 8 quoted lines
> It says
> * refs/heads/my_branch02: not updating to non-fast forward branch
> 'my_branch02' of ../stg_branch
>
> my_branch02 is the StGit managed branch from stg_branch, other
> normal branchs are getting merged. Since this is StGit managed, fast
> forward merge is not possible, I guess. So how can I pull in the
> StGit managed changes to web.git repository?

Either prefix each of the refspects with a + (as in +my_branch01:my_branch01), or use the -f flag (which has the same effect as using + on all the refspecs). This will allow the refs to be overwritten even if it's not a fast-forward.

You have to do this with StGit-managed branches, since StGit is essentially just a convenient way to rebase commits.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Rajkumar S
Message 2 of 2 in “Cloning an StGit repository”
  1. Rajkumar SOct 18, 2007
  2. Karl HasselströmOct 18, 2007

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.