From: "Peter Eriksen" <s022018@student.dtu.dk>
To: git@vger.kernel.org
Subject: Re: [RFC/PATCH] git-prune: never lose objects reachable from our refs.
Date: Fri, 9 Dec 2005 20:39:22 +0100 [thread overview]
Message-ID: <20051209193922.GA31228@ebar091.ebar.dtu.dk> (raw)
In-Reply-To: <7vmzja91gp.fsf_-_@assigned-by-dhcp.cox.net>
On Thu, Dec 08, 2005 at 11:25:10PM -0800, Junio C Hamano wrote:
> Explicit <head> arguments to git-prune replaces, instead of
> extends, the list of heads used for reachability analysis by
> fsck-objects. By giving a subset of heads by mistake, objects
> reachable only from other heads can be removed, resulting in a
> corrupted repository.
>
> This commit stops replacing the list of heads, and makes the
> command line arguments to add to them instead for safety.
Shouldn't the first sentence be "Explicit <head> arguments to git-prune
extends, instead of replaces,...", that is, interchange the words
extends and replaces? Did I miss something?
Peter
next prev parent reply other threads:[~2005-12-09 20:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 23:28 [PATCH 0/17] Documentation fixes in response to my previous listing Nikolai Weibull
2005-12-08 23:28 ` [PATCH 1/17] Document the --non-empty command-line option to git-pack-objects Nikolai Weibull
2005-12-08 23:28 ` [PATCH 2/17] Fix the description of --utf8 and --keep to git-am Nikolai Weibull
2005-12-08 23:28 ` [PATCH 3/17] Use uniform description for the '--' option Nikolai Weibull
2005-12-08 23:28 ` [PATCH 4/17] Documentation/git-commit.txt: Add long options and -- to documentation Nikolai Weibull
2005-12-08 23:28 ` [PATCH 5/17] Documentation/git-verify-pack.txt: added documentation for -- Nikolai Weibull
2005-12-08 23:28 ` [PATCH 6/17] Document the [<head>...] and -- arguments to git-prune Nikolai Weibull
2005-12-08 23:28 ` [PATCH 7/17] Documentation/git-cvsimport.txt: Fix a slight glitch in description heading Nikolai Weibull
2005-12-08 23:28 ` [PATCH 8/17] Documentation/git-cherry-pick: Add --replay and --no-commit Nikolai Weibull
2005-12-08 23:28 ` [PATCH 9/17] Add documentation for git-revert and git-cherry-pick Nikolai Weibull
2005-12-08 23:28 ` [PATCH 10/17] Add documentation for the --topo-order option to git-show-branch Nikolai Weibull
2005-12-08 23:28 ` [PATCH 11/17] Documentation/git-format-patch.txt: Add --signoff, --check, and long option-names Nikolai Weibull
2005-12-08 23:28 ` [PATCH 12/17] Documentation/git-ls-remote.txt: Add -h and -t Nikolai Weibull
2005-12-08 23:28 ` [PATCH 13/17] Documentation/git-repack.txt: Add -l and -n Nikolai Weibull
2005-12-08 23:28 ` [PATCH 14/17] Documentation/git-http-fetch.txt: Document the commit-id argument Nikolai Weibull
2005-12-08 23:28 ` [PATCH 15/17] Documentation/git-update-server-info.txt: Add -f alias for --force to documentation Nikolai Weibull
2005-12-08 23:28 ` [PATCH 16/17] Documentation/git-tag.txt: Fix the order of sections (DESCRIPTION should come before OPTIONS) Nikolai Weibull
2005-12-08 23:28 ` [PATCH 17/17] Documentation/git-read-tree.txt: Add --reset to SYNOPSIS Nikolai Weibull
2005-12-08 23:49 ` [PATCH 6/17] Document the [<head>...] and -- arguments to git-prune Junio C Hamano
2005-12-08 23:56 ` Junio C Hamano
2005-12-09 0:28 ` Junio C Hamano
2005-12-09 7:25 ` [RFC/PATCH] git-prune: never lose objects reachable from our refs Junio C Hamano
2005-12-09 19:39 ` Peter Eriksen [this message]
2005-12-09 20:38 ` Junio C Hamano
2005-12-09 0:50 ` [PATCH 6/17] Document the [<head>...] and -- arguments to git-prune Nikolai Weibull
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=20051209193922.GA31228@ebar091.ebar.dtu.dk \
--to=s022018@student.dtu.dk \
--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).