From: Jakub Narebski <jnareb@gmail.com>
To: "Catalin Marinas" <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: StGIT 0.13 recognizes but not list packed StGIT controlled branches
Date: Mon, 19 Nov 2007 12:57:07 +0100 [thread overview]
Message-ID: <200711191257.09158.jnareb@gmail.com> (raw)
In-Reply-To: <b0943d9e0711190320r28224763t5a6c9ed7758a12b3@mail.gmail.com>
Catalin Marinas wrote:
> On 18/11/2007, Jakub Narebski <jnareb@gmail.com> wrote:
>
> > I use Stacked GIT 0.13 with git 1.5.3.5 (and Python 2.4.3).
> > StGIT does recognize old StGIT branches (and converts them),
> > but "stg branch -l" list only one branch. I guess that is
> > cause by the fact that all the rest of branches are packed.
>
> Have you tried the latest StGIT snapshot? We added support for this
> and it will be available in 0.14 (to be released pretty soon).
Would it work with Python 2.4.3? Yes, I know I should upgrade my
Linux distribution (I use now Aurox 11.1, which is based on Fedora
Core 4)...
> > Another StGIT question: how to check if given branch is controlled
> > by StGIT (needed for my bash prompt)?
>
> 'stg branch -l' lists the branches and marks those controlled by
> StGIT. For a simple test, just use a command which would fail on
> non-stgit branches (stg id base). Yet another way is to check for the
> presence of '.git/patches/<branch>'.
Thanks. 'stg id base' is quite a lot slower than
'test -e "$(git rev-parse --git-dir)/patches/$branch"', and it _does_
matter in prompt creating.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-11-19 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 23:05 StGIT 0.13 recognizes but not list packed StGIT controlled branches Jakub Narebski
2007-11-19 0:00 ` Junio C Hamano
2007-11-19 11:20 ` Catalin Marinas
2007-11-19 11:57 ` Jakub Narebski [this message]
2007-11-19 13:15 ` Catalin Marinas
2007-11-19 17:43 ` Jakub Narebski
2007-11-19 17:51 ` Catalin Marinas
2007-11-19 18:26 ` Jakub Narebski
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=200711191257.09158.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.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).