user/sven/git.git/git-lost-found.sh, branch v1.8.0.2

lost-found: use git rev-parse -q

2008-12-03T22:27:17Z

Signed-off-by: Miklos Vajna Signed-off-by: Junio C Hamano

Merge branch 'ph/parseopt-sh'

2007-11-18T05:39:37Z

* ph/parseopt-sh: git-quiltimport.sh fix --patches handling git-am: -i does not take a string parameter. sh-setup: don't let eval output to be shell-expanded. git-sh-setup: fix parseopt `eval` string underquoting Give git-am back the ability to add Signed-off-by lines. git-rev-parse --parseopt scripts: Add placeholders for OPTIONS_SPEC Migrate git-repack.sh to use git-rev-parse --parseopt Migrate git-quiltimport.sh to use git-rev-parse --parseopt Migrate git-checkout.sh to use git-rev-parse --parseopt --keep-dashdash Migrate git-instaweb.sh to use git-rev-parse --parseopt Migrate git-merge.sh to use git-rev-parse --parseopt Migrate git-am.sh to use git-rev-parse --parseopt Migrate git-clone to use git-rev-parse --parseopt Migrate git-clean.sh to use git-rev-parse --parseopt. Update git-sh-setup(1) to allow transparent use of git-rev-parse --parseopt Add a parseopt mode to git-rev-parse to bring parse-options to shell scripts.

Deprecate git-lost-found

2007-11-08T01:12:53Z

"git fsck" learnt the option "--lost-found" in v1.5.3-rc0~5, to make "git lost-found" obsolete. It is time to deprecate "git lost-found". Signed-off-by: Johannes Schindelin Signed-off-by: Junio C Hamano

scripts: Add placeholders for OPTIONS_SPEC

2007-11-06T09:50:02Z

--text follows this line-- These commands currently lack OPTIONS_SPEC; allow people to easily list with "git grep 'OPTIONS_SPEC=$'" what they can help improving. Signed-off-by: Junio C Hamano

Rewrite "git-frotz" to "git frotz"

2007-07-03T05:52:14Z

This uses the remove-dashes target to replace "git-frotz" to "git frotz". Signed-off-by: Junio C Hamano

Fix lost-found to show commits only referenced by reflogs

2007-04-05T22:00:03Z

Prior to 1.5.0 the git-lost-found utility was useful to locate commits that were not referenced by any ref. These were often amends, or resets, or tips of branches that had been deleted. Being able to locate a 'lost' commit and recover it by creating a new branch was a useful feature in those days. Unfortunately 1.5.0 added the reflogs to the reachability analysis performed by git-fsck, which means that most commits users would consider to be lost are still reachable through a reflog. So most (or all!) commits are reachable, and nothing gets output from git-lost-found. Now git-fsck can be told to ignore reflogs during its reachability analysis, making git-lost-found useful again to locate commits that are no longer referenced by a ref itself, but may still be referenced by a reflog. Signed-off-by: Shawn O. Pearce Signed-off-by: Junio C Hamano

git-fsck-objects is now synonym to git-fsck

2007-01-29T00:33:58Z

Signed-off-by: Junio C Hamano

lost-found: use fsck-objects --full

2006-07-28T05:15:01Z

Signed-off-by: Junio C Hamano

git-lost-found: Usage string clean-up, emit usage string at incorrect invocation

2005-12-14T10:53:44Z

Signed-off-by: Fredrik Kuivinen Signed-off-by: Junio C Hamano

lost-found: make it operable from a subdirectory.

2005-11-29T07:13:03Z

Signed-off-by: Junio C Hamano