From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Aneesh Kumar" <aneesh.kumar@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>, kha@treskal.com
Subject: Re: stg branch command failures.
Date: Wed, 10 Oct 2007 09:47:15 +0100 [thread overview]
Message-ID: <b0943d9e0710100147n5bcd52d4waa8b52efb41b4270@mail.gmail.com> (raw)
In-Reply-To: <cc723f590710092031w87511dfl6ee3b728375f0815@mail.gmail.com>
On 10/10/2007, Aneesh Kumar <aneesh.kumar@gmail.com> wrote:
> Both the below commands doesn't work
>
> stg branch --rename review test-large-file
> stg branch -c review v2.6.23-rc9
>
> It throws error
> fatal: Needed a single revision
What version of GIT are you using? I started getting this message
recently as well but only noticed it when renaming patches. However,
the operation completes successfully (the message is displayed by GIT,
not StGIT). I'll have to investigate.
--
Catalin
prev parent reply other threads:[~2007-10-10 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 3:31 stg branch command failures Aneesh Kumar
2007-10-10 7:34 ` Karl Hasselström
2007-10-10 8:47 ` Catalin Marinas [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=b0943d9e0710100147n5bcd52d4waa8b52efb41b4270@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/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).