From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: deprecating more
Date: Fri, 16 Sep 2005 19:29:35 -0700 [thread overview]
Message-ID: <7vr7boe8a8.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0509161856260.26803@g5.osdl.org> (Linus Torvalds's message of "Fri, 16 Sep 2005 18:59:24 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> It's obviously much less powerful than "git-whatchanged", or just about
> any combination of git-rev-list + git-diff-tree.
>
> So drop it.
I'm happy to hear an argument to drop it, but I would like to
make sure that you do realize that git-whatchanged is not a
convenient way to truly "export" for later recreation of
identical repository, due to its indentation and truncation
behaviour. Not that *I* think that matters.
What do you think about the other commands I mentioned?
next prev parent reply other threads:[~2005-09-17 2:29 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 ` deprecating more Junio C Hamano
2005-09-17 1:58 ` Horst von Brand
2005-09-17 1:59 ` Linus Torvalds
2005-09-17 2:29 ` Junio C Hamano [this message]
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=7vr7boe8a8.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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.