# stg branch --create test v2.6.24-rc1 doesn't work 4 messages from 2007-10-26 to 2007-11-02. Participants: Aneesh Kumar, Catalin Marinas. Thread: https://gitlist.dev/t/10472 ## Aneesh Kumar, 2007-10-26 10:42 Subject: stg branch --create test v2.6.24-rc1 doesn't work Message-ID: URL: https://gitlist.dev/e/cc723f590710260342t5fd0bdc3nc1ea5198cea1a604%40mail.gmail.com ``` $ 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]$ git log Throws an error/warning in the above command. Also import then gives [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 ``` ## Catalin Marinas, 2007-10-29 17:11 Subject: Re: stg branch --create test v2.6.24-rc1 doesn't work Message-ID: URL: https://gitlist.dev/e/b0943d9e0710291011p11bd8901udeb758fa653610bc%40mail.gmail.com In-Reply-To: ``` On 26/10/2007, Aneesh Kumar 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]$ git log > > > Throws an error/warning in the above command. > > Also import then gives > > [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 What version of StGIT are you using? You could try 'stg branch --create test v2.6.24-rc1^{commit} but I thought latest StGIT adds this by default. -- Catalin ``` ## Aneesh Kumar, 2007-10-30 04:50 Subject: Re: stg branch --create test v2.6.24-rc1 doesn't work Message-ID: URL: https://gitlist.dev/e/cc723f590710292150y752034c7x5642758eb51a7ed6%40mail.gmail.com In-Reply-To: ``` On 10/29/07, Catalin Marinas wrote: > On 26/10/2007, Aneesh Kumar 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]$ git log > > > > > > Throws an error/warning in the above command. > > > > Also import then gives > > > > [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 > > What version of StGIT are you using? > Latest stgit. d4356ac6143757131b58c95ca5c6a7b386cc6087 > You could try 'stg branch --create test v2.6.24-rc1^{commit} but I > thought latest StGIT adds this by default. > -aneesh ``` ## Catalin Marinas, 2007-11-02 09:24 Subject: Re: stg branch --create test v2.6.24-rc1 doesn't work Message-ID: URL: https://gitlist.dev/e/b0943d9e0711020224q6e4b6acn5879183dd14b6fff%40mail.gmail.com In-Reply-To: ``` On 26/10/2007, Aneesh Kumar 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 ```