From: Linus Torvalds <torvalds@osdl.org>
To: Aubrey <aubreylee@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Quick question: how to generate a patch?
Date: Mon, 27 Feb 2006 08:32:36 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602270830330.22647@g5.osdl.org> (raw)
In-Reply-To: <6d6a94c50602270818k5f82bb8ft68a19899db3db636@mail.gmail.com>
On Tue, 28 Feb 2006, Aubrey wrote:
>
> No, what I did was just "git clone" one repository to my local directory.
> And entered the local directory to modify one file I wanted.
> Then I run "git diff > my.patch". The "my.patch" was supposed to
> contain one file diff information. But it contained the all the files,
> including which were not changed.
It really should "just have worked". Can you show what the diff actually
looked like, and your exact command history?
If it was something like
git clone remote-repo localdir
cd localdir
vi somefile
git diff
then you did everything right, and if it gives any diff other than your
changes to "somefile", something is buggy. Need more info.
Does "git diff" and "git diff HEAD" give different results, btw?
Linus
next prev parent reply other threads:[~2006-02-27 16:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 14:57 Quick question: how to generate a patch? Aubrey
2006-02-27 15:28 ` Andreas Ericsson
2006-02-27 16:04 ` Linus Torvalds
2006-02-27 16:18 ` Aubrey
2006-02-27 16:32 ` Linus Torvalds [this message]
2006-02-27 17:02 ` Aubrey
2006-02-27 17:09 ` Andreas Ericsson
2006-02-27 17:18 ` Aubrey
2006-02-27 17:28 ` Linus Torvalds
2006-02-28 1:55 ` Aubrey
2006-02-28 2:09 ` Linus Torvalds
2006-02-28 2:48 ` Aubrey
2006-02-27 17:19 ` Linus Torvalds
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=Pine.LNX.4.64.0602270830330.22647@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=aubreylee@gmail.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 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).