From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Misc patches for grub2
Date: Sun, 27 Jul 2008 00:36:43 -0400 [thread overview]
Message-ID: <1217133403.15984.4.camel@ct> (raw)
In-Reply-To: <200807251458.23483.Chris.Knadle@coredump.us>
On Fri, 2008-07-25 at 14:58 -0400, Chris Knadle wrote:
> On Friday 25 July 2008, Bean wrote:
> > On Sat, Jul 26, 2008 at 1:19 AM, Chris Knadle <Chris.Knadle@coredump.us>
> wrote:
> > > On Friday 25 July 2008, Bean wrote:
> > >> 4. rename appleloader command to bootcamp
> > >>
> > >> The name appleloader may be a little confusing, bootcamp seems to be a
> > >> better choice.
> > >
> > > Rather than patching all of the content from appleloader.c to
> > > bootcamp.c you may want to consider doing a 'git-mv' to rename the file
> > > instead.
> >
> > Yes, i do use git-mv to rename files, but when i use git-diff to
> > generate the patch, it looks like this.
>
> Oh... Okay I think I understand why. 'git-diff -M' can detect the renames
> and just list them, but the 'patch' command can't use that to incorporate the
> renames, which is probably why the -M behavior isn't the default.
>
> So... nevermind. ;-)
Our main repository is in Subversion, so whoever applies the patch
should use "svn move" to keep the contiguous file history. Unlike git,
which trusts the contents in the first place, Subversion is more
sensitive to whatever users are telling it.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-07-27 4:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 16:38 [PATCH] Misc patches for grub2 Bean
2008-07-25 17:19 ` Chris Knadle
2008-07-25 17:45 ` Bean
2008-07-25 18:58 ` Chris Knadle
2008-07-27 4:36 ` Pavel Roskin [this message]
2008-07-25 20:53 ` Robert Millan
2008-07-26 4:28 ` Bean
2008-07-27 4:55 ` Pavel Roskin
2008-07-27 6:00 ` Bean
2008-07-27 7:05 ` Pavel Roskin
2008-07-27 7:14 ` Bean
2008-07-27 7:20 ` Pavel Roskin
2008-07-27 7:30 ` Bean
2008-07-27 7:33 ` Pavel Roskin
2008-07-27 13:51 ` Bean
2008-08-05 10:36 ` Marco Gerards
2008-08-05 14:14 ` Bean
2008-08-05 17:30 ` Colin D Bennett
2008-08-05 20:11 ` Robert Millan
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=1217133403.15984.4.camel@ct \
--to=proski@gnu.org \
--cc=grub-devel@gnu.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.