From: William Morgan <wmorgan-git@masanjin.net>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-walkthrough-add script
Date: Fri, 04 Jan 2008 18:37:34 -0800 [thread overview]
Message-ID: <1199500441-sup-4067@south> (raw)
In-Reply-To: <20080104210751.GB26248@coredump.intra.peff.net>
Excerpts from Jeff King's message of Fri Jan 04 13:07:51 -0800 2008:
> But if you have interface improvement suggestions for "git-add -i" or
> "git-add -p", I'm sure they would be well-received (post-1.5.4
> release, of course).
Not to show off my git newbness any more than necessary, but when I run
both git-add -i and git-add -p, I see exactly the same output and
interface. Are they meant to be different? This is with both master and
next branches of the git repo.
~/devel/sup$ ~/devel/git/installed/bin/git-add -i
staged unstaged path
1: unchanged +1/-0 doc/TODO
2: unchanged +1/-1 lib/sup/message.rb
3: unchanged +28/-43 lib/sup/thread.rb
*** Commands ***
1: status 2: update 3: revert 4: add untracked
5: patch 6: diff 7: quit 8: help
What now>
Bye.
~/devel/sup$ ~/devel/git/installed/bin/git-add -p
staged unstaged path
1: unchanged +1/-0 doc/TODO
2: unchanged +1/-1 lib/sup/message.rb
3: unchanged +28/-43 lib/sup/thread.rb
*** Commands ***
1: status 2: update 3: revert 4: add untracked
5: patch 6: diff 7: quit 8: help
What now>
Bye.
--
William <wmorgan-git@masanjin.net>
next prev parent reply other threads:[~2008-01-05 2:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 6:14 git-walkthrough-add script William Morgan
2008-01-04 7:26 ` Jeff King
2008-01-04 18:31 ` William Morgan
2008-01-04 21:07 ` Jeff King
2008-01-05 2:37 ` William Morgan [this message]
2008-01-05 2:50 ` Junio C Hamano
2008-01-05 2:55 ` Junio C Hamano
2008-01-05 3:02 ` William Morgan
2008-01-05 4:08 ` Pedro Melo
2008-01-04 23:26 ` Pedro Melo
2008-01-04 23:28 ` Junio C Hamano
2008-01-05 0:02 ` William Morgan
2008-01-05 0:17 ` Pedro Melo
2008-01-05 1:00 ` Miklos Vajna
2008-01-05 2:54 ` William Morgan
2008-01-05 3:43 ` Jeff King
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=1199500441-sup-4067@south \
--to=wmorgan-git@masanjin.net \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.