From: "Shawn O. Pearce" <spearce@spearce.org>
To: Marc Weber <marco-oweber@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] add--interactive: added [c]heckout
Date: Mon, 6 Oct 2008 07:51:37 -0700 [thread overview]
Message-ID: <20081006145137.GC8203@spearce.org> (raw)
In-Reply-To: <353e718308129444268e61f251dab769761f095f.1223304141.git.marco-oweber@gmx.de>
Marc Weber <marco-oweber@gmx.de> wrote:
> this is convinient for cygwin users not using rxvt.
>
> added last (before quit and help) to not break menu layout and keep exisiting
> numbering
>
> Signed-off-by: Marc Weber <marco-oweber@gmx.de>
> ---
> git-add--interactive | 1129 ++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 1129 insertions(+), 0 deletions(-)
> create mode 100755 git-add--interactive
>
> diff --git a/git-add--interactive b/git-add--interactive
> new file mode 100755
> index 0000000..2e7fa55
> --- /dev/null
> +++ b/git-add--interactive
Uhm, what is this patch against? git.git? If so why are we creating
a new 1129 line script named something erily close to a script we
already have?
--
Shawn.
next prev parent reply other threads:[~2008-10-06 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 15:26 What about renaming ga -i [r]evert to [r]eset ? Marc Weber
2008-10-05 16:41 ` Jeff King
2008-10-05 21:46 ` [PATCH 2] renaming git add -i [r]evert -> reset and adding gitt add -i [c]heckout Marc Weber
2008-10-05 22:11 ` Jeff King
2008-10-06 14:46 ` [PATCH 1/2] add--interactive: rename [r]evert command to [r]eset Marc Weber
2008-10-06 14:49 ` [PATCH 2/2] add--interactive: added [c]heckout Marc Weber
2008-10-06 14:51 ` Shawn O. Pearce [this message]
2008-10-06 15:55 ` Marc Weber
2008-10-06 14:55 ` [PATCH 1/2] add--interactive: rename [r]evert command to [r]eset Shawn O. Pearce
2008-10-06 15:51 ` Marc Weber
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=20081006145137.GC8203@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=marco-oweber@gmx.de \
/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).