John Keeping j...@keeping.me.uk writes:
Hmm, I hadn't realised that specifying -p would disable the --raw.
I still find the last sentence of the original patch slightly awkward
though. How about
New users are encouraged to use linkgit:git-log[1] instead. The
`whatchanged` command
On Fri, Aug 09, 2013 at 01:57:19PM -0700, Junio C Hamano wrote:
John Keeping j...@keeping.me.uk writes:
+New users are encouraged to use linkgit:git-log[1] instead. The
+`whatchanged` command is essentially the same as linkgit:git-log[1]
+run with different defaults that shows a --raw
Junio C Hamano wrote:
Documentation/git-whatchanged.txt | 41
---
1 file changed, 8 insertions(+), 33 deletions(-)
Looks good. Thanks for doing this.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to
of the
command is not hurting anybody, other than the new people who may
stumble upon both and wonder what their differences are. By clearly
indicating that these two are essentially the same, we would help
the new people without harming anybody.
-- 8 --
Subject: [PATCH] whatchanged: document its
people without harming anybody.
-- 8 --
Subject: [PATCH] whatchanged: document its historical nature
Encourage new users to use 'log' instead. These days, these
commands are unified and just have different defaults.
'git log' only allowed you to view the log messages and no diffs
when
John Keeping j...@keeping.me.uk writes:
+New users are encouraged to use linkgit:git-log[1] instead. The
+`whatchanged` command is essentially the same as linkgit:git-log[1]
+run with different defaults that shows a --raw diff outputat the
s/outputat/output at/
Thanks.
Although I wonder
6 matches
Mail list logo
