Re: What's cooking in git.git (Apr 2011, #01; Sun, 3)

Michael J Gruber [off-list ref] writes:

quoted

[New Topics]
* jc/rev-list-options-fix (2011-04-01) 1 commit
  (merged to 'next' on 2011-04-03 at 91f19de)
 + "log --cherry-pick" documentation regression fix

We should merge this before -rc1, but there might be other similar
breakages in the text flow due to the same f98fd43 (git-log.txt,
rev-list-options.txt: put option blocks in proper order, 2011-03-08).

I rechecked and didn't find any other mis-references. Some commit
limiting options mention commit formatters like "--pretty", but I deem
that to be okay without an explicit "see below".

Thanks.

quoted

* mg/doc-revisions-txt (2011-04-01) 3 commits
 - revisions.txt: language improvements
 - revisions.txt: structure with a labelled list
 - revisions.txt: consistent use of quotes

Most parts looked reasonable except for some nits.

Should I resubmit or have you squashed that in already?

I don't think I squashed anything in to this series.

quoted

* mg/show-without-prune (2011-04-01) 1 commit
 - builtin/show: do not prune by pathspec
 (this branch uses mg/reflog-with-options.)

I wanted to like this, but it still feels like too much magic.

...with a little less magic suggested now (act on single no-walk rev only).

An alternative might be to give an advice message only when a single
no-walk rev with given with a single pathspec and we didn't produce any
output.

quoted

* mg/sha1-path-advise (2011-03-31) 2 commits
 - sha1_name: Suggest commit:./file for path in subdir
 - t1506: factor out test for "Did you mean..."

Should I resubmit with "commit:./file" only, or is that too late anyways?

The topic is too late for 1.7.5 either way, and I am starting to like your
"aka" better than before.  I am tempted to merge this to "next" only to
give it wider exposure now, so that other people know what we are talking
about when we have to decide what to do after 1.7.5.