From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: deprecating more
Date: Fri, 16 Sep 2005 18:31:54 -0700 [thread overview]
Message-ID: <7vzmqceayd.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vd5n8fqso.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 16 Sep 2005 18:04:23 -0700")
Junio C Hamano <junkio@cox.net> writes:
> Is anybody actually using this program? If not I'd like to
> deprecate it now and remove it before we hit 1.0. As far as I
> can tell it is not very useful.
The same goes for the following programs:
git-diff-helper
git-diff-stages
git-export
git-rev-tree
Among them, I could be talked into keeping git-export on the
condition that we will add a counterpart git-import that can
read git-export output and recreate an identical repository
[*1*]; without something like that, I doubt its usefulness,
especially since "git-whatchanged" is far more useful for
everyday use.
[Footnote]
*1* which I think actually is impossible without fixing
git-export first so that it exports the initial commit. I may
be mistaken.
next prev parent reply other threads:[~2005-09-17 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 1:04 git-diff-stages? Junio C Hamano
2005-09-17 1:31 ` Junio C Hamano [this message]
2005-09-17 1:58 ` deprecating more Horst von Brand
2005-09-17 1:59 ` Linus Torvalds
2005-09-17 2:29 ` Junio C Hamano
2005-09-17 2:50 ` Linus Torvalds
2005-09-17 5:28 ` Junio C Hamano
2005-09-17 6:13 ` Tony Luck
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=7vzmqceayd.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.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 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).