threads / discuss / 13429

mismatch between doc and program in git commit -u (--untracked-files)

Subject: mismatch between doc and program in git commit -u (--untracked-files)

## tl;dr

3 messages between May 8, 2008 and May 9, 2008.

replies: 2people: 2as markdown or json

Sitaram Chamarty· May 8, 2008, 10:10 UTC · lore
Hello,

The doc for commit says "-u" is a suitable abbreviation for --untracked-files, but only the latter works.

I'll submit a patch, but being new, I thought I'd ask which is correct -- the doc or the code?

Thanks,
Sitaram
Jeff King· May 8, 2008, 16:13 UTC · re: Sitaram Chamarty · lore

Re: mismatch between doc and program in git commit -u (--untracked-files)

On Thu, May 08, 2008 at 03:40:14PM +0530, Sitaram Chamarty wrote:
Show 5 quoted lines
> The doc for commit says "-u" is a suitable abbreviation for
> --untracked-files, but only the latter works.
> 
> I'll submit a patch, but being new, I thought I'd ask which is correct
> -- the doc or the code?
Looks like it got lost in the C rewrite of git-commit:
  $ git grep untracked-files builtin-commit.c
  builtin-commit.c:       OPT_BOOLEAN(0, "untracked-files", &untracked_files, "show all untracked files"),
  $ git grep -B2 contrib/examples/git-commit.sh
  contrib/examples/git-commit.sh- -u|--u|--un|--unt|--untr|--untra|--untrac|--untrack|--untracke|\
  contrib/examples/git-commit.sh- --untracked|--untracked-|--untracked-f|--untracked-fi|--untracked-fil|\
  contrib/examples/git-commit.sh: --untracked-file|--untracked-files)

So it should probably be supported. The patch is a one-liner, but I'll leave it as an exercise for you. :)

-Peff
Sitaram Chamarty· May 9, 2008, 17:26 UTC · re: Jeff King · lore

Re: mismatch between doc and program in git commit -u (--untracked-files)

On Thu, May 8, 2008 at 9:43 PM, Jeff King <peff@peff.net> wrote:
Show 6 quoted lines
> On Thu, May 08, 2008 at 03:40:14PM +0530, Sitaram Chamarty wrote:
>> The doc for commit says "-u" is a suitable abbreviation for
>> --untracked-files, but only the latter works.
>>
>> I'll submit a patch, but being new, I thought I'd ask which is correct
>> -- the doc or the code?
> So it should probably be supported. The patch is a one-liner, but I'll
> leave it as an exercise for you. :)
:)

Due to my using gmail which doesn't leave the whitespace alone, I had to resort to the clumsy trick of doing a "sendmail -oi -t -f sitaramc@gmail.com" from my home machine, and vger's SMTP listener decided to greylist the mail.

It'll come through eventually, assuming I keep my laptop switched on long enough!

(Although pobox.com seems to have accepted it OK.)
Sitaram

← back to recent threads