All of lore.kernel.org
 help / color / mirror / Atom feed
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 03:05:02 -0400	[thread overview]
Message-ID: <1217142302.16601.40.camel@ct> (raw)
In-Reply-To: <ca0f59980807262300s3c29bac3ga7e0a9ecde86edfb@mail.gmail.com>

On Sun, 2008-07-27 at 14:00 +0800, Bean wrote:
> Hi,
> 
> On Sun, Jul 27, 2008 at 12:55 PM, Pavel Roskin <proski@gnu.org> wrote:
> > 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.
> 
> I use git-mv to move files, which is the equivalence of "svn move".
> But when I use git-diff to generate the patch, it looks as if files
> are truncated. I can use git-diff -M to create a patch that shows the
> renames, but it's not usable by patch.

That's why I'm asking "whoever applies the patch" to be careful.

> > IMHO that even worse.  Using a trademarked name like "linux" to run the
> > trademarked software could be justified.  But using a trademarked name
> > to replace or emulate the original software is asking for a big trouble.
> >
> > Admittedly, I'm not a lawyer, but some people are, and it's better not
> > to attract their attention.
> 
> In fact, it doesn't replace bootcamp, it calls the service provided by
> bootcamp. But anyway, it's not a big deal, I can just keep the name
> appleloader.

Fine.

> BTW, any comment about the other changes ?

Why do we need "crc"?  If there are chances that it will be used for
security, we should be using SHA-1.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-07-27  7:05 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
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 [this message]
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=1217142302.16601.40.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.