From: "J. Bruce Fields" <bfields@fieldses.org>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Chuck Lever <cel@netapp.com>,
Catalin Marinas <catalin.marinas@gmail.com>,
git@vger.kernel.org
Subject: Re: Diffs "from" working directory
Date: Sun, 20 Nov 2005 12:43:59 -0500 [thread overview]
Message-ID: <20051120174359.GA24177@fieldses.org> (raw)
In-Reply-To: <200511201817.15780.blaisorblade@yahoo.it>
On Sun, Nov 20, 2005 at 06:17:15PM +0100, Blaisorblade wrote:
> I've given a look at commit fcc1ad70be5ff89996358b6d770cd229fec2a3ba, and
> while it may or may not be the right thing to do, there's a misunderstanding
> at the base.
What misunderstanding? Could you quote it?
> For instance, in the stg tree, before that patch, I can do:
>
> $ echo ciao >> README
> $ stg diff -r HEAD:
> $ stg diff -r HEAD
> diff --git a/README b/README
> index 184ded8..adb3970 100644
> --- a/README
> +++ b/README
> @@ -12,3 +12,4 @@ StGIT commands.
>
> For the latest version see http://www.procode.org/stgit/
> For a tutorial see http://wiki.procode.org/cgi-bin/wiki.cgi/StGIT_Tutorial
> +ciao
That's a diff *to* the working directory. My complaint was that there
wasn't a convenient way to get a diff *from* the working directory.
It's nice to have a convenient shorthand for the current working
directory, and since there's already a shorthand for the HEAD ("HEAD")
it seemed more sensible to make "" the current working directory.
It's a minor point, but it seems convenient.
--b.
next parent reply other threads:[~2005-11-20 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200511201817.15780.blaisorblade@yahoo.it>
2005-11-20 17:43 ` J. Bruce Fields [this message]
2005-11-20 18:13 ` Diffs "from" working directory Linus Torvalds
2005-11-20 20:58 ` J. Bruce Fields
2005-11-21 1:53 ` Chuck Lever
2005-11-21 21:28 ` Catalin Marinas
2005-11-21 21:40 ` Junio C Hamano
2005-11-21 21:45 ` Catalin Marinas
2005-11-22 5:15 ` Chuck Lever
2005-11-22 5:33 ` Linus Torvalds
2005-11-22 18:03 ` Chuck Lever
2005-11-22 18:32 ` Linus Torvalds
2005-11-22 10:35 ` Catalin Marinas
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=20051120174359.GA24177@fieldses.org \
--to=bfields@fieldses.org \
--cc=blaisorblade@yahoo.it \
--cc=catalin.marinas@gmail.com \
--cc=cel@netapp.com \
--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 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.