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

Re: How to do a fast-forward merge without a checkout?

From
knittl <knittl89@googlemail.com>
Date
Jul 18, 2011, 16:08 UTC
Message-ID
<CACx-yZ1H5UfA9SeaGy-Ph+20BEsewJe7_78wQsr92Y09skSWHA@mail.gmail.com>
In-Reply-To
<CAF_dkJCvtVqoDmRXMy23ZnZL6iUAVX0nNA9Ev6e4zvBp9mfTpg@mail.gmail.com>
On Mon, Jul 18, 2011 at 4:18 PM, Patrick Doyle <wpdster@gmail.com> wrote:
Show 12 quoted lines
> […]
>
> $ git push
> […]
> To somehost:path/to/repo
>   e1004df..bad8767  wpd -> wpd
>  ! [rejected]        master -> master (non-fast-forward)
> error: failed to push some refs to 'somehost:path/to/repo'
> To prevent you from losing history, non-fast-forward updates were rejected
> Merge the remote changes (e.g. 'git pull') before pushing again.  See the
> 'Note about fast-forwards' section of 'git push --help' for details.
>

another way to avoid pushing the master branch is to explicitely name the branch to push (wpd):

    $ git push origin wpd
cheers, daniel
-- 
typed with http://neo-layout.org
myFtPhp -- visit http://myftphp.sf.net -- v. 0.4.7 released!
Previous: Patrick DoyleNext: Patrick Doyle
Message 4 of 6 in “How to do a fast-forward merge without a checkout?”
  1. Patrick DoyleJul 18, 2011
  2. Johannes SixtJul 18, 2011
  3. Patrick DoyleJul 18, 2011
  4. knittlJul 18, 2011
  5. Patrick DoyleJul 18, 2011
  6. knittlJul 18, 2011

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.