From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: GSoC status report
Date: Sat, 21 Jul 2007 03:12:10 +0200 [thread overview]
Message-ID: <200707210312.11745.jnareb@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707201118550.14781@racer.site>
Johannes Schindelin wrote:
> FWIW this is the list of scripts that I would like to see converted by the
> end of the year (feel free to object), ordered by their size:
>
> verify-tag, reset, repack, tag, checkout, rebase, bisect,
> rebase--interactive, am, commit.
I thought that verify-tag would be put into git-tag, with git-verify-tag
being alias to "git tag --verify" or something like that.
What about git-revert and git-cherry-pick (it is one script)? Or are you
simply concentrating on the tools you need most in common workflow?
Thanks for the reply
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-07-21 1:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 8:24 GSoC status report Jakub Narebski
2007-07-20 8:34 ` Shawn O. Pearce
2007-07-20 10:37 ` Johannes Schindelin
2007-07-21 1:12 ` Jakub Narebski [this message]
2007-07-21 1:24 ` Johannes Schindelin
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=200707210312.11745.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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 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).