All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: git@vger.kernel.org
Subject: Re: git faq : draft and rfc
Date: Thu, 16 Feb 2006 08:32:37 -0600	[thread overview]
Message-ID: <E1F9kBR-0005D0-7F@jdl.com> (raw)
In-Reply-To: 22e91bb0602151636r2e70e60cpa5038f4b6caccc9c@mail.gmail.com


> I'll try to add questions from the archives of this ml, I'm also open
> to any suggestions.

This is sort of the "missing" paragraph from the "git-checkout"
man page.  It's there now, but in the "-m" option.

jdl



Q.  Why won't git let me change to a different branch
    using "git checkout <branch>" or "git checkout -b <branch>"?
    Instead it just says:
        fatal: Entry 'foo.c' not uptodate. Cannot merge.

A.  You have changes to files in your working directory that
    will be overwritten, removed or otherwise lost if the checkout
    and change to the new branch were to proceed.  To fix this
    you may either check your changes in, create a patch of your
    changes and revert your files, or use the "-m" flag like this:
        git checkout -m -b my-branch

             reply	other threads:[~2006-02-16 14:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 14:32 Jon Loeliger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-16  0:36 git faq : draft and rfc Thomas Riboulet
2006-02-16  4:04 ` Martin Langhoff
2006-02-16 13:22   ` Johannes Schindelin
2006-02-16 13:38     ` Bertrand Jacquin
2006-02-16 15:00       ` Johannes Schindelin
2006-02-16  7:50 ` Alan Chandler
2006-02-16 15:18 ` Petr Baudis
2006-02-16 23:52   ` Thomas Riboulet
2006-02-20 13:30     ` Bertrand Jacquin
2006-02-20 13:41       ` Bertrand Jacquin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1F9kBR-0005D0-7F@jdl.com \
    --to=jdl@jdl.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.