delta/git.git/builtin/prune-packed.c, branch ce/https-public-key-pinning

standardize usage info string format

2015-01-14T17:32:04+00:00

This patch puts the usage info strings that were not already in docopt-
like format into docopt-like format, which will be a litle easier for
end users and a lot easier for translators. Changes include:

- Placing angle brackets around fill-in-the-blank parameters
- Putting dashes in multiword parameter names
- Adding spaces to [-f|--foobar] to make [-f | --foobar]
- Replacing * with [...]

Signed-off-by: Alex Henrie 
Reviewed-by: Matthieu Moy 
Signed-off-by: Junio C Hamano

prune-packed: use for_each_loose_file_in_objdir

2014-10-16T17:10:40+00:00

This saves us from manually traversing the directory
structure ourselves.

Signed-off-by: Jeff King 
Signed-off-by: Junio C Hamano

prune-packed: fix minor memory leak

2014-09-15T18:37:43+00:00

We form all of our directories in a strbuf, but never release it.

Signed-off-by: Jeff King 
Signed-off-by: Junio C Hamano

i18n: mark all progress lines for translation

2014-02-24T17:08:37+00:00

Signed-off-by: Nguyễn Thái Ngọc Duy 
Signed-off-by: Junio C Hamano

prune-packed: use strbuf to avoid having to worry about PATH_MAX

2013-12-17T18:43:30+00:00

A/very/long/path/to/.git that becomes exactly PATH_MAX bytes long
after suffixed with /objects/??/??38-hex??, would have overflown
the on-stack pathname[] buffer.

Noticed-by:  Michael Haggerty 
Signed-off-by: Junio C Hamano

prune-packed: avoid implying "1" is DRY_RUN in prune_packed_objects()

2013-05-28T16:20:54+00:00

Commit b60daf0 (Make git-prune-packed a bit more chatty. - 2007-01-12)
changes the meaning of prune_packed_objects()'s argument, from "dry
run or not dry run" to a bitmap.

It however forgot to update prune_packed_objects() caller in
builtin/prune.c to use new DRY_RUN macro. It's fine (for a long time!)
but there is a risk that someday someone may change the value of
DRY_RUN to something else and builtin/prune.c suddenly breaks. Avoid
that possibility.

While at there, change "opts == VERBOSE" to "opts & VERBOSE" as there
is no obvious reason why we only be chatty when DRY_RUN is not set.

Signed-off-by: Nguyễn Thái Ngọc Duy 
Signed-off-by: Junio C Hamano

i18n: prune-packed: mark parseopt strings for translation

2012-08-20T19:23:19+00:00

Signed-off-by: Nguyễn Thái Ngọc Duy 
Signed-off-by: Junio C Hamano

fix deletion of .git/objects sub-directories in git-prune/repack

2012-03-07T18:24:33+00:00

Both git-prune and git-repack (and thus, git-gc) try to rmdir while
holding a DIR* handle on the directory.  This can leave dangling
empty directories in the .git/objects on platforms where directory
cannot be removed while they are open.

First call closedir() and then rmdir(); that is more logical ordering.

Reported-by: John Chen 
Reported-by: Stefan Naewe 
Signed-off-by: Karsten Blees 
Improved-and-Acked-by: Johannes Sixt 
Signed-off-by: Junio C Hamano

Move 'builtin-*' into a 'builtin/' subdirectory

2010-02-22T22:29:41+00:00

This shrinks the top-level directory a bit, and makes it much more
pleasant to use auto-completion on the thing. Instead of

	[torvalds@nehalem git]$ em buil
	Display all 180 possibilities? (y or n)
	[torvalds@nehalem git]$ em builtin-sh
	builtin-shortlog.c     builtin-show-branch.c  builtin-show-ref.c
	builtin-shortlog.o     builtin-show-branch.o  builtin-show-ref.o
	[torvalds@nehalem git]$ em builtin-shor
	builtin-shortlog.c  builtin-shortlog.o
	[torvalds@nehalem git]$ em builtin-shortlog.c

you get

	[torvalds@nehalem git]$ em buil		[type]
	builtin/   builtin.h
	[torvalds@nehalem git]$ em builtin		[auto-completes to]
	[torvalds@nehalem git]$ em builtin/sh	[type]
	shortlog.c     shortlog.o     show-branch.c  show-branch.o  show-ref.c     show-ref.o
	[torvalds@nehalem git]$ em builtin/sho		[auto-completes to]
	[torvalds@nehalem git]$ em builtin/shor	[type]
	shortlog.c  shortlog.o
	[torvalds@nehalem git]$ em builtin/shortlog.c

which doesn't seem all that different, but not having that annoying
break in "Display all 180 possibilities?" is quite a relief.

NOTE! If you do this in a clean tree (no object files etc), or using an
editor that has auto-completion rules that ignores '*.o' files, you
won't see that annoying 'Display all 180 possibilities?' message - it
will just show the choices instead.  I think bash has some cut-off
around 100 choices or something.

So the reason I see this is that I'm using an odd editory, and thus
don't have the rules to cut down on auto-completion.  But you can
simulate that by using 'ls' instead, or something similar.

Signed-off-by: Linus Torvalds 
Signed-off-by: Junio C Hamano