From: Catalin Marinas <catalin.marinas@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Stacked Git 0.15
Date: Sun, 25 Oct 2009 17:13:03 +0000 [thread overview]
Message-ID: <b0943d9e0910251013v19fb39b7we412e7f734c2755f@mail.gmail.com> (raw)
In-Reply-To: <m34opoe5t6.fsf@localhost.localdomain>
2009/10/25 Jakub Narebski <jnareb@gmail.com>:
> Catalin Marinas <catalin.marinas@gmail.com> writes:
>
>> StGit is a Python application providing functionality similar to Quilt
>> (i.e. pushing/popping patches to/from a stack) on top of Git. These
>> operations are performed using Git commands, and the patches are
>> stored as Git commit objects, allowing easy merging of the StGit
>> patches into other repositories using standard Git functionality.
>>
>> Download: http://download.gna.org/stgit/stgit-0.15.tar.gz
>> Main repository: git://repo.or.cz/stgit.git
>> Project homepage: http://www.procode.org/stgit/
>> Mailing list: git@vger.kernel.org (please use "StGit" in the subject)
>> Bug tracker: https://gna.org/bugs/?group=stgit
>
> Is there RPM or SRPM (src.rpm) available somewhere? Or does tarball
> include *.spec file, or an rpm target?
Late last night when running my release script I realised that
setup.py no longer accepts the --prefix=/usr option I used for RPMs.
I'll try to build one in the next couple of days (I wasn't even sure
anyone was using it).
--
Catalin
next prev parent reply other threads:[~2009-10-25 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 22:41 [ANNOUNCE] Stacked Git 0.15 Catalin Marinas
2009-10-24 23:20 ` Jakub Narebski
2009-10-25 17:13 ` Catalin Marinas [this message]
2009-10-26 10:32 ` Catalin Marinas
2009-10-26 13:49 ` Karl Wiberg
2009-10-26 16:23 ` Catalin Marinas
2009-11-02 10:05 ` Felipe Contreras
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=b0943d9e0910251013v19fb39b7we412e7f734c2755f@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).