From: Jeff King <peff@peff.net>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Testing for commit reachability through plumbing commands
Date: Thu, 6 Mar 2014 15:23:19 -0500 [thread overview]
Message-ID: <20140306202319.GB29659@sigill.intra.peff.net> (raw)
In-Reply-To: <CACPiFCJLyE6XC9dY_eawe2y9gS4YsPdTbqkKAd0dcPXd5-eMCg@mail.gmail.com>
On Thu, Mar 06, 2014 at 12:17:34PM -0500, Martin Langhoff wrote:
> I have a shell script that trims old history on a cronjob. This is for
> a repo that is used to track reports that have limited "life" (like
> logs). Old history is trimmed with grafts pointing to an empty "root"
> commit.
>
> Right now, info/graft grows unbound. I am looking for a way to trim
> unreachable grafts, I would like to be able to say something like:
>
> git is-reachable treeish
How about:
git rev-list --objects --all |
cut -d' ' -f1 |
grep $(git rev-parse treeish)
Add "--reflog" to the rev-list invocation if you want to catch things
referenced by the reflog, too.
If you're looking for a commit, you can drop the "--objects", and it
will run much faster.
-Peff
prev parent reply other threads:[~2014-03-06 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 17:17 Testing for commit reachability through plumbing commands Martin Langhoff
2014-03-06 19:17 ` Andreas Schwab
2014-03-06 19:29 ` Martin Langhoff
2014-03-06 20:23 ` Jeff King [this message]
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=20140306202319.GB29659@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@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).