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

Re: Cherry-picking to remote branches

From
VMiklos <vmiklos@frugalware.org>
Date
Jul 6, 2007, 15:01 UTC
Message-ID
<20070706150155.GV32766@genesis.frugalware.org>
In-Reply-To
<a2e879e50707060739s4c8e751dj494618d3d545277b@mail.gmail.com>
Na Fri, Jul 06, 2007 at 09:39:47AM -0500, Sean Kelley <svk.sweng@gmail.com> pisal(a):
Show 28 quoted lines
>> > git checkout -b stable linux-stable/master
>> >
>> > git cherry-pick  b3b1eea69a   (a commit from linux-devel)
>> >
>> > git push linux-stable
>> >
>> > error: remote 'refs/heads/master' is not a strict subset of local ref
>> > 'refs/heads/master'. maybe you are not up-to-date and need to pull
>> > first?
>> > error: failed to push to 'git://mysite.com/data/git/linux-stable.git'
>>
>> Since you are obviously only interested in pushing the stable branch, why
>> don't you
>>
>>         git push linux-stable stable
>>
>> Hm?
>>
>> If you do not specify which branches to push, "git push" will find all
>> refnames which are present both locally and remotely, and push those.
>> Evidently, however, your local "master" disagrees with the remote
>> "master".
>
> It is not entirely clear to me from the documentation.  So I was
> trying to cobble together something that seemed to make sense.  I want
> to work from the devel clone.  On occasion I want to cherry-pick
> changesets and push those to the stable branch.  I don't want
> everything that goes into devel to go into stable.
what about this?
        git push linux-stable stable:master
VMiklos
-- 
developer of Frugalware Linux - http://frugalware.org
Previous: Sean KelleyNext: Sean Kelley
Message 4 of 6 in “Cherry-picking to remote branches”
  1. Sean KelleyJul 6, 2007
  2. Johannes SchindelinJul 6, 2007
  3. Sean KelleyJul 6, 2007
  4. VMiklosJul 6, 2007
  5. Sean KelleyJul 6, 2007
  6. Sean KelleyJul 7, 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.