From: "Karl Hasselström" <kha@treskal.com>
To: Pavel Roskin <proski@gnu.org>
Cc: git@vger.kernel.org, Catalin Marinas <catalin.marinas@gmail.com>,
Yann Dirson <ydirson@altern.org>
Subject: [StGIT PATCH 0/2] Teach StGIT to survive git-gc
Date: Fri, 10 Aug 2007 05:23:02 +0200 [thread overview]
Message-ID: <20070810031949.19791.54562.stgit@yoghurt> (raw)
In-Reply-To: <20070809203957.GA14441@diana.vm.bytemark.co.uk>
... and here's the fix, and a test.
Note that while this is fairly intrusive (and took quite some time to
debug), it's also a rather high-priority fix, since git-gc will break
StGIT just fine even without the DAG patches.
You can also get this from git://repo.or.cz/stgit/kha.git.
--
Karl Hasselström, kha@treskal.com
www.treskal.com/kalle
next prev parent reply other threads:[~2007-08-10 3:23 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
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 ` Karl Hasselström [this message]
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=20070810031949.19791.54562.stgit@yoghurt \
--to=kha@treskal.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=proski@gnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.