From: Catalin Marinas <catalin.marinas@gmail.com>
To: Mark Wooding <mdw@distorted.org.uk>
Cc: git@vger.kernel.org
Subject: Prune-safe StGIT (was Re: Two crazy proposals for changing git's diff commands)
Date: Mon, 13 Feb 2006 22:00:14 +0000 [thread overview]
Message-ID: <43F1016E.5070203@gmail.com> (raw)
In-Reply-To: <slrnduphvr.2i8.mdw@metalzone.distorted.org.uk>
Mark Wooding wrote:
> (I really look forward to a StGIT which can withstand git-prune.)
Since there were a few requests for this feature, I pushed it to the
public repository (and also included it in the latest snapshot).
As it was discussed a few months ago, the top id of each patch
(including the popped ones) is added to the
.git/refs/patches/<branch>/<patch> file. The git-prune command will
preserve these objects and their referents, making even the unapplied
patches safe. There is another advantage with this approach - gitk shows
the patch name for every corresponding commit.
Running any command (apart from help) on the current branch would create
the initial references. You would need to do the same with all the other
branches. Since this is a new feature, make sure you have backups before
pruning (though it worked OK for me).
--
Catalin
next prev parent reply other threads:[~2006-02-13 22:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 0:29 Two crazy proposals for changing git's diff commands Carl Worth
2006-02-09 1:05 ` Linus Torvalds
2006-02-09 1:21 ` Linus Torvalds
2006-02-09 23:07 ` Carl Worth
2006-02-09 23:40 ` Junio C Hamano
2006-02-09 1:35 ` Junio C Hamano
2006-02-09 1:21 ` Junio C Hamano
2006-02-09 1:30 ` Linus Torvalds
2006-02-09 1:37 ` Junio C Hamano
2006-02-10 9:05 ` Junio C Hamano
2006-02-10 20:32 ` Comments on "status -v" (was: Two crazy proposals for changing git's diff commands) Carl Worth
2006-02-10 21:09 ` Comments on "status -v" Junio C Hamano
2006-02-10 21:35 ` Linus Torvalds
2006-02-10 22:12 ` Junio C Hamano
2006-02-10 22:51 ` Petr Baudis
2006-02-10 23:26 ` Junio C Hamano
2006-02-09 23:44 ` Two crazy proposals for changing git's diff commands Carl Worth
2006-02-10 0:13 ` Junio C Hamano
2006-02-10 1:24 ` Carl Worth
2006-02-10 2:24 ` Junio C Hamano
2006-02-10 3:18 ` Carl Worth
2006-02-10 17:06 ` Mark Wooding
2006-02-13 9:23 ` Catalin Marinas
2006-02-13 22:00 ` Catalin Marinas [this message]
2006-02-10 19:36 ` Kent Engstrom
2006-02-11 19:25 ` Junio C Hamano
2006-02-12 12:00 ` [PATCH] Add howto about separating topics kent
2006-02-12 3:15 ` Two crazy proposals for changing git's diff commands J. Bruce Fields
2006-02-12 3:48 ` Junio C Hamano
2006-02-09 16:44 ` Tim Larson
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=43F1016E.5070203@gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=mdw@distorted.org.uk \
/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).