git/Documentation/git.txt, branch v2.3.8Mirror of https://git.kernel.org/pub/scm/git/git.git/
https://git.shady.money/git/atom?h=v2.3.82015-05-11T21:36:31ZGit 2.3.82015-05-11T21:36:31ZJunio C Hamanogitster@pobox.com2015-05-11T21:36:31Zurn:sha1:9a3d637541a5b6fcd84b6f5fa057e597d1696460
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Git 2.3.72015-04-27T19:25:36ZJunio C Hamanogitster@pobox.com2015-04-27T19:25:36Zurn:sha1:16018ae5fb368151f3eff13730cf089b63f41962
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Git 2.3.62015-04-21T19:17:09ZJunio C Hamanogitster@pobox.com2015-04-21T19:17:09Zurn:sha1:ba63bfaa59ee41bd679286a594cc643b5a53c48d
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Git 2.3.52015-03-31T21:57:10ZJunio C Hamanogitster@pobox.com2015-03-31T21:57:10Zurn:sha1:52735a689270bb1de94eb3de198594b36caed9bb
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Merge branch 'nd/doc-git-index-version' into maint2015-03-28T16:33:13ZJunio C Hamanogitster@pobox.com2015-03-28T16:33:13Zurn:sha1:2217579cde1d3a96446f8435f6fb4a89925d599a
Doc clean-up.
* nd/doc-git-index-version:
git.txt: list index versions in plain English
Merge branch 'jk/prune-with-corrupt-refs' into maint2015-03-28T16:33:06ZJunio C Hamanogitster@pobox.com2015-03-28T16:33:06Zurn:sha1:9f389aa4920f147a6314719741b47074b2e4b727
"git prune" used to largely ignore broken refs when deciding which
objects are still being used, which could spread an existing small
damage and make it a larger one.
* jk/prune-with-corrupt-refs:
refs.c: drop curate_packed_refs
repack: turn on "ref paranoia" when doing a destructive repack
prune: turn on ref_paranoia flag
refs: introduce a "ref paranoia" flag
t5312: test object deletion code paths in a corrupted repository
git.txt: list index versions in plain English2015-03-24T15:06:00ZNguyễn Thái Ngọc Duypclouds@gmail.com2015-03-24T00:28:33Zurn:sha1:70320541ec8727fe57d0bb29a196edef71cae840
At the first look, a user may think the default version is "23". Even
with UNIX background, there's no reference anywhere close that may
indicate this is glob or regex.
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Git 2.3.42015-03-23T18:27:27ZJunio C Hamanogitster@pobox.com2015-03-23T18:27:27Zurn:sha1:3a52578eef9b65ad449853e4a3a923d8e1eb2a22
Signed-off-by: Junio C Hamano <gitster@pobox.com>
refs: introduce a "ref paranoia" flag2015-03-20T19:40:49ZJeff Kingpeff@peff.net2015-03-20T18:43:06Zurn:sha1:49672f26d9a3826a6a74c6ff4d2409b7b0c74495
Most operations that iterate over refs are happy to ignore
broken cruft. However, some operations should be performed
with knowledge of these broken refs, because it is better
for the operation to choke on a missing object than it is to
silently pretend that the ref did not exist (e.g., if we are
computing the set of reachable tips in order to prune
objects).
These processes could just call for_each_rawref, except that
ref iteration is often hidden behind other interfaces. For
instance, for a destructive "repack -ad", we would have to
inform "pack-objects" that we are destructive, and then it
would in turn have to tell the revision code that our
"--all" should include broken refs.
It's much simpler to just set a global for "dangerous"
operations that includes broken refs in all iterations.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Git 2.3.32015-03-14T05:57:25ZJunio C Hamanogitster@pobox.com2015-03-14T05:57:25Zurn:sha1:bb8577532add843833ebf8b5324f94f84cb71ca0
Signed-off-by: Junio C Hamano <gitster@pobox.com>