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 18:43:41 +0100 [thread overview]
Message-ID: <200711191843.43247.jnareb@gmail.com> (raw)
In-Reply-To: <b0943d9e0711190515x3f58748bm224366ddb292755d@mail.gmail.com>
On Mon, 19 November 2007, Catalin Marinas wrote:
> On 19/11/2007, Jakub Narebski <jnareb@gmail.com> wrote:
>> Catalin Marinas wrote:
>>>
>>> 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)...
>
> Yes, it works with Python 2.4. We deprecated the Python 2.3 support.
I was worried that it would require Python 2.5 (IIRC some stgit RPM
had it in requires)
By the way, does StGIT write something meaningful by default in reflog
messages? Because now my reflog looks like this:
2162:[autoconf@git]# git reflog
407d6dc... HEAD@{0}:
5a46eb5... HEAD@{1}:
[...]
ea55960... HEAD@{15}:
8f5d6b4... HEAD@{16}:
15bb3f6... HEAD@{17}: checkout: moving from master to autoconf
8aff795... HEAD@{18}: pull origin: Merge made by recursive.
It would be really nice if StGIT wrote something meaningfull when
updating ref, like "stg refresh: <something>", or "stg rebase: <sth>"...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-11-19 17:44 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
2007-11-19 13:15 ` Catalin Marinas
2007-11-19 17:43 ` Jakub Narebski [this message]
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=200711191843.43247.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).