From: "Justin P. mattock" <justinmattock@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Rename imacfb.txt to efifb.txt and change imacfb to
Date: Sun, 28 Mar 2010 19:08:41 +0000 [thread overview]
Message-ID: <4BAFA939.7080000@gmail.com> (raw)
In-Reply-To: <10f740e81003281154i4885f559s3f6ac79f1e697a3e@mail.gmail.com>
On 03/28/2010 11:54 AM, Geert Uytterhoeven wrote:
> On Sun, Mar 28, 2010 at 19:43, Justin P. Mattock
> <justinmattock@gmail.com> wrote:
>> Rename imacfb.txt to efifb.txt since imacfb was moved to
>> efifb,and change imacfb to efifb.
>> Note:I used git rm for imacfb.txt, but
>> git renamed this file to efifb.txt after everything was said and
>> done, not sure if this is correct or not.
>
> Git doesn't track renames. It just notices a new file is very similar
> (in this case identical)
> to a deleted one.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
that's what happened i.g. I did git rm imacfb.txt
then did a git add efifb.txt
then git commit
then git said rename in the end
I've never submitted an add/delete so hopefully
this is o.k.
Justin P. Mattock
WARNING: multiple messages have this Message-ID (diff)
From: "Justin P. mattock" <justinmattock@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Rename imacfb.txt to efifb.txt and change imacfb to efifb.
Date: Sun, 28 Mar 2010 12:08:41 -0700 [thread overview]
Message-ID: <4BAFA939.7080000@gmail.com> (raw)
In-Reply-To: <10f740e81003281154i4885f559s3f6ac79f1e697a3e@mail.gmail.com>
On 03/28/2010 11:54 AM, Geert Uytterhoeven wrote:
> On Sun, Mar 28, 2010 at 19:43, Justin P. Mattock
> <justinmattock@gmail.com> wrote:
>> Rename imacfb.txt to efifb.txt since imacfb was moved to
>> efifb,and change imacfb to efifb.
>> Note:I used git rm for imacfb.txt, but
>> git renamed this file to efifb.txt after everything was said and
>> done, not sure if this is correct or not.
>
> Git doesn't track renames. It just notices a new file is very similar
> (in this case identical)
> to a deleted one.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
that's what happened i.g. I did git rm imacfb.txt
then did a git add efifb.txt
then git commit
then git said rename in the end
I've never submitted an add/delete so hopefully
this is o.k.
Justin P. Mattock
next prev parent reply other threads:[~2010-03-28 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 17:43 [PATCH] Rename imacfb.txt to efifb.txt and change imacfb to efifb Justin P. Mattock
2010-03-28 17:43 ` Justin P. Mattock
2010-03-28 18:54 ` [PATCH] Rename imacfb.txt to efifb.txt and change imacfb to Geert Uytterhoeven
2010-03-28 18:54 ` [PATCH] Rename imacfb.txt to efifb.txt and change imacfb to efifb Geert Uytterhoeven
2010-03-28 19:08 ` Justin P. mattock [this message]
2010-03-28 19:08 ` Justin P. mattock
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=4BAFA939.7080000@gmail.com \
--to=justinmattock@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@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.