From: Pavel Roskin <proski@gnu.org>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org, Catalin Marinas <catalin.marinas@gmail.com>,
Yann Dirson <ydirson@altern.org>
Subject: Re: 'pu' branch for StGIT
Date: Thu, 09 Aug 2007 09:24:43 -0400 [thread overview]
Message-ID: <1186665883.28228.31.camel@dv> (raw)
In-Reply-To: <20070809073801.GA31482@diana.vm.bytemark.co.uk>
On Thu, 2007-08-09 at 09:38 +0200, Karl Hasselström wrote:
> I take it this all means you're actually using my branch? What's your
> opinion on its usefulness?
Well, I tried it, and then ran a script to update all local
repositories. It converted everything to "version 3", so I'm sort of
stuck with it. If the "version 3" code is not committed to the mainline
StGIT, I'll have to convert my repositories back or even re-fetch them.
I have noticed two problems so far, but I cannot tell is they are
specific to the "pu" branch.
1) Undead patches.
StGIT finds a patch I deleted long ago and shows it as unapplied. It
cannot be deleted by "stg delete" because some files are missing.
$ stg delete at76_usb
Traceback (most recent call last):
File "/home/proski/bin/stg", line 43, in <module>
main()
File "home/proski/lib/python2.5/site-packages/stgit/main.py", line 284, in main
File "home/proski/lib/python2.5/site-packages/stgit/commands/delete.py", line 76, in func
File "home/proski/lib/python2.5/site-packages/stgit/stack.py", line 1227, in delete_patch
File "home/proski/lib/python2.5/site-packages/stgit/stack.py", line 1209, in delete_patch_data
File "home/proski/lib/python2.5/site-packages/stgit/stack.py", line 160, in delete
OSError: [Errno 2] No such file or directory: '.git/patches/wireless-dev/patches/at76_usb'
That's Linux repository, and I'm on wireless-dev branch. There is a
file .git/patches/wireless-dev/trash/at76_usb containing "None". There
are two other files in that directory, but they have some SHA1 hashes.
There is also a file .git/patches/wireless-dev/patchorder, which
contains "at76_usb".
I was updating the repository by "stg pull", there were two patches,
"at76_usb" being first. It couldn't be merged, so I deleted it. I
deleted the other patch as well, since I new it was applied upstream.
After another "stg pull" at76_usb became "undead".
I cannot reproduce it on another repository.
2) Invisible branches.
StGIT stopped showing other branches. It's always showing the same
branch, although it can switch to other branches:
[proski@dv linux-2.6]$ stg branch --list
Available branches:
> s wireless-dev |
[proski@dv linux-2.6]$ stg branch wireless-2.6
Checking for changes in the working directory ... done
Switching to branch "wireless-2.6" ... done
[proski@dv linux-2.6]$ stg branch --list
Available branches:
s wireless-dev |
[proski@dv linux-2.6]$ stg branch linus
Checking for changes in the working directory ... done
Switching to branch "linus" ... done
[proski@dv linux-2.6]$ stg branch --list
Available branches:
s wireless-dev |
[proski@dv linux-2.6]$ stg init
stg init: linus already initialized
[proski@dv linux-2.6]$
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-08-09 13:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 2:20 'pu' branch for StGIT Karl Hasselström
2007-08-07 2:38 ` Shawn O. Pearce
2007-08-08 5:03 ` Pavel Roskin
2007-08-08 9:20 ` Karl Hasselström
2007-08-08 21:39 ` Karl Hasselström
2007-08-08 22:18 ` Pavel Roskin
2007-08-08 23:23 ` Karl Hasselström
2007-08-09 0:10 ` Pavel Roskin
2007-08-09 7:38 ` Karl Hasselström
2007-08-09 13:24 ` Pavel Roskin [this message]
2007-08-09 14:18 ` Karl Hasselström
2007-08-09 14:24 ` Karl Hasselström
2007-08-09 16:33 ` Pavel Roskin
2007-08-09 20:39 ` Karl Hasselström
2007-08-10 3:23 ` [StGIT PATCH 0/2] Teach StGIT to survive git-gc Karl Hasselström
2007-08-10 3:23 ` [StGIT PATCH 1/2] New test: make sure that StGIT can handle packed refs Karl Hasselström
2007-08-10 3:23 ` [StGIT PATCH 2/2] Don't touch ref files manually Karl Hasselström
2007-08-21 13:23 ` Catalin Marinas
2007-08-21 15:58 ` Karl Hasselström
2007-08-21 16:09 ` Karl Hasselström
2007-08-21 16:12 ` Johannes Sixt
2007-08-21 16:38 ` Karl Hasselström
2007-08-21 16:46 ` Karl Hasselström
2007-08-21 20:48 ` Karl Hasselström
2007-08-23 14:04 ` Catalin Marinas
2007-08-09 21:31 ` 'pu' branch for StGIT Catalin Marinas
2007-08-10 0:30 ` Karl Hasselström
2007-08-12 22:47 ` Pavel Roskin
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=1186665883.28228.31.camel@dv \
--to=proski@gnu.org \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=ydirson@altern.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 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).