From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 3/5] make "git unpack-file" a built-in
Date: Fri, 22 Jan 2010 10:26:12 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001221022121.13231@localhost.localdomain> (raw)
In-Reply-To: <7vmy06vwvy.fsf@alter.siamese.dyndns.org>
On Fri, 22 Jan 2010, Junio C Hamano wrote:
> > {
> > unsigned char sha1[20];
> >
> > - git_extract_argv0_path(argv[0]);
> > -
> > if (argc != 2 || !strcmp(argv[1], "-h"))
> > usage("git unpack-file <sha1>");
> > if (get_sha1(argv[1], sha1))
> > die("Not a valid object name %s", argv[1]);
> >
> > - setup_git_directory();
>
> This will now require "git unpack-file -h" to be run in a git controlled
> directory, so strictly speaking it changes behaviour.
>
> Not that anybody would care that much, though.
Heh. You didn't notice the same change in the merge-tree conversion that
you already accepted ;)
Yeah, any usage messages will now run after setup for the commands that do
the whole RUN_SETUP thing. That's pack-redundant, unpack-file, mktag,
merge-index and merge-tree. So they'll now report "Not a git repository"
before they report invalid arguments.
Linus
next prev parent reply other threads:[~2010-01-22 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 16:22 [Patch 0/5] make more commands built-in Linus Torvalds
2010-01-22 16:25 ` [PATCH 1/5] make "merge-index" a built-in Linus Torvalds
2010-01-22 16:26 ` PATCH 2/5] make "mktag" " Linus Torvalds
2010-01-22 16:27 ` [PATCH 3/5] make "git unpack-file" " Linus Torvalds
2010-01-22 16:28 ` [PATCH 4/5] make "git pack-redundant" " Linus Torvalds
2010-01-22 16:31 ` [PATCH 5/5] make "index-pack" " Linus Torvalds
2010-01-22 18:04 ` [PATCH 3/5] make "git unpack-file" " Junio C Hamano
2010-01-22 18:26 ` Linus Torvalds [this message]
2010-01-22 16:33 ` PATCH 2/5] make "mktag" " Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.00.1001221022121.13231@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).