From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Aneesh Kumar" <aneesh.kumar@gmail.com>
Cc: kha@treskal.com, "Git Mailing List" <git@vger.kernel.org>
Subject: Re: stg branch --create test v2.6.24-rc1 doesn't work
Date: Fri, 2 Nov 2007 09:24:59 +0000 [thread overview]
Message-ID: <b0943d9e0711020224q6e4b6acn5879183dd14b6fff@mail.gmail.com> (raw)
In-Reply-To: <cc723f590710260342t5fd0bdc3nc1ea5198cea1a604@mail.gmail.com>
On 26/10/2007, Aneesh Kumar <aneesh.kumar@gmail.com> wrote:
> $ stg branch --create test v2.6.24-rc1
> Checking for changes in the working directory ... done
> Don't know how to determine parent branch from "v2.6.24-rc1"
> Branch "test" created
[...]
> [test@linux-review-ext]$ stg import
> /home/opensource/patches/ext4-patch-queue/ext4_mballoc_freespace_accounting_fix.patch
> Checking for changes in the working directory ... done
> fatal: cebdeed27b068dcc3e7c311d7ec0d9c33b5138c2 is not a valid 'commit' object
> stg import: git-commit-tree failed with code 128
The problem is that a tag id is used as the head of the stack rather
than the corresponding commit id. I modified StGIT to get the commit
id (and, as I said, you can work around this in the meantime by
passing "v2.6.24-rc1^{commit}" to the branch command).
I'll push the changes tonight but I have to solve the branch deletion
as it is left in an inconsistent state after import (and --force
should be able to deal with it but it doesn't).
--
Catalin
prev parent reply other threads:[~2007-11-02 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 10:42 stg branch --create test v2.6.24-rc1 doesn't work Aneesh Kumar
2007-10-29 17:11 ` Catalin Marinas
2007-10-30 4:50 ` Aneesh Kumar
2007-11-02 9:24 ` 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=b0943d9e0711020224q6e4b6acn5879183dd14b6fff@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).