From: Jacob Helwig <jacob.helwig@gmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Git <git@vger.kernel.org>
Subject: Re: Odd error when doing "clone && cd && checkout -b"
Date: Wed, 3 Feb 2010 05:25:58 -0800 [thread overview]
Message-ID: <20100203132558.GA4595@vfb-9.home> (raw)
In-Reply-To: <4B692863.9000409@viscovery.net>
On Tue, Feb 2, 2010 at 23:40, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Jacob Helwig schrieb:
>> vfb-9 ~/tmp % git clone git://github.com/rich97/CakeCMP.git && cd CakeCMP && git checkout -b permissions-rewrite origin/permissions-rewrite
>> Initialized empty shared Git repository in /home/jhe/tmp/CakeCMP/.git/
>> remote: Counting objects: 1508, done.
>> remote: Compressing objects: 100% (1432/1432), done.
>> remote: Total 1508 (delta 256), reused 1235 (delta 60)
>> Receiving objects: 100% (1508/1508), 844.43 KiB | 104 KiB/s, done.
>> Resolving deltas: 100% (256/256), done.
>> fatal: git checkout: updating paths is incompatible with switching branches.
>> Did you intend to checkout 'origin/permissions-rewrite' which can not be resolved as commit?
>
> Or did you intend to track 'origin/permission-rewrite' instead ;-)
>
> -- Hannes
>
> PS: Please don't set Mail-Followup-To for this list.
>
Well, I _thought_ I had used the exact same command for the "checkout
-b". Obviously, this is not the case. Bah. That's what I get for
trying to do anything so late.
Apparently Mutt defaults to setting the Mail-Followup-To, if you've let
it know about a list. Anyway...that's been fixed.
-Jacob
prev parent reply other threads:[~2010-02-03 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 7:00 Odd error when doing "clone && cd && checkout -b" Jacob Helwig
2010-02-03 7:40 ` Johannes Sixt
2010-02-03 13:25 ` Jacob Helwig [this message]
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=20100203132558.GA4595@vfb-9.home \
--to=jacob.helwig@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).