Shawn Pearce <spearce@xxxxxxxxxxx> writes:
> Of course that's not what the code does, because if either the
> old or the new object is no longer in the ODB you are pruning away
> the log entry. I cannot however come up with a better name than
> --expire-lost. :-(
How about --expire-unreachable?
> I'm thinking that we may want the 'expire' subcommand to simply be
> implied by '--expire' instead.
After coding this, my conclusion is the same as yours, but
reasoning behind it is slightly different.
To have 'expire' action as a subcommand to 'git-reflog' is from
implementor's point of view, and is a horrible organization from
the UI standpoint. To the end users, it may be easier to have a
single 'git-gc' command that runs these commands with reasonable
set of defaults:
- rerere gc
- reflog expire --all
- (possibly) repack -a -d
- prune
If we go that route, it probably is not even necessary to
advertise that 'expire' is a subcommand of reflog. The users
would not run it from the command line; it is an implementation
detail of 'git-gc' command.
> Needing a subcommand like 'git reflog show HEAD' is just a lot
> of typing[*1*].
I am very interested in seeing how 'git reflog show HEAD' would
show the reflog entries. I've tried showing it just like log
family shows (it is reasonably easy; you build the list of revs
out of reflog entries and feed them to 'git-show' machinery),
and while it works, it is unusable for the purpose of seeing
which ones are the lost ones (amended commits and rebased branch
remnants).
The best I came up with is still my "show-branch --reflog" so
far. You really need to show not just the commit title but how
they topologically relate to the commits on the surviving
branch, and I think having something graphical or semi-graphical
is a must.
> I would also say maybe we want to make --dry-run the default, with
> a final message which tells the user that if they really want to
> make it possible to throw away the commits printed above then
> restart the expire operation.
I am moderately negative on that. Nobody does it like that;
prune, branch -d, tag -d,...
> I'd like to take a stab at the log display code for the reflog
> command, but I'd also really like to port forward (aka rewrite)
> that mmap window code I keep saying I'll work on, but never quite
> seem to do...
After today's pread() thing, I was also wondering about that too
;-).
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html