From: "Carlos Rica" <jasampler@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Make builtin-reset.c use parse_options.
Date: Sun, 2 Mar 2008 13:37:38 +0100 [thread overview]
Message-ID: <1b46aba20803020437p2a5128a5wfee3e98c32c1a610@mail.gmail.com> (raw)
In-Reply-To: <7vir05x2di.fsf@gitster.siamese.dyndns.org>
On Sun, Mar 2, 2008 at 3:53 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Carlos Rica <jasampler@gmail.com> writes:
>
> > Signed-off-by: Carlos Rica <jasampler@gmail.com>
>
> Hmmm. "git reset -h" now defaults to --hard?
>
> It somehow feels a bit risky for new people. I dunno.
>
I don't understand what do you mean.
Option -h just prints the options and exits.
Do you mean that the help message is wrong?
Also, there is a test to check that "git reset" defaults to
--mixed ('--mixed reset to HEAD should unadd the files'
only run a "git reset" without parameters),
and changing it to do a --hard reset makes the tests to fail.
If there's a change in the behaviour of the command,
please, show me how to test it. I cannot see anything
wrong now.
-- Carlos
next prev parent reply other threads:[~2008-03-02 12:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 16:29 [PATCH] Make builtin-reset.c use parse_options Carlos Rica
2008-03-02 2:53 ` Junio C Hamano
2008-03-02 12:37 ` Carlos Rica [this message]
2008-03-02 16:18 ` Junio C Hamano
2008-03-03 14:07 ` Carlos Rica
2008-03-03 17:07 ` Pierre Habouzit
2008-03-03 22:40 ` Junio C Hamano
2008-03-04 9:45 ` Pierre Habouzit
2008-03-02 16:32 ` Johannes Schindelin
2008-03-02 9:40 ` Alex Riesen
2008-03-02 12:54 ` Carlos Rica
2008-03-02 15:55 ` Alex Riesen
2008-03-02 18:40 ` Carlos Rica
2008-03-02 21:38 ` Alex Riesen
2008-03-03 14:39 ` Carlos Rica
-- strict thread matches above, loose matches on Subject: below --
2008-03-04 22:11 Carlos Rica
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=1b46aba20803020437p2a5128a5wfee3e98c32c1a610@mail.gmail.com \
--to=jasampler@gmail.com \
--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).