This is the mail archive of the
mailing list for the glibc project.
Re: How should files be moved in the glibc repository
- From: Steve Ellcey <sellcey at caviumnetworks dot com>
- To: Andreas Schwab <schwab at linux-m68k dot org>, Steve Ellcey <sellcey at cavium dot com>
- Cc: <libc-alpha at sourceware dot org>
- Date: Mon, 28 Nov 2016 10:34:17 -0800
- Subject: Re: How should files be moved in the glibc repository
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Steve dot Ellcey at cavium dot com;
- References: <201611281745.uASHjLIB015416@sellcey-lt.caveonetworks.com> <email@example.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On Mon, 2016-11-28 at 19:00 +0100, Andreas Schwab wrote:
> On Nov 28 2016, Steve Ellcey <firstname.lastname@example.org> wrote:
> > 'git mv' or a 'git rm / git add' to move these files? Or does it
> > matter?
> It doesn't matter. Both do exactly the same.
I found my problem. I was doing 'git diff' and not 'git diff HEAD'.
The 'git diff' command did not capture renames or deletes when creating
a patch, the 'git diff HEAD' command does capture them and then when I
apply that patch the old files are no longer there.