From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: git crapps out with {kernel_version}/usr/include
Date: Sat, 11 Sep 2010 11:38:16 -0700 [thread overview]
Message-ID: <4C8BCC98.4070506@gmail.com> (raw)
In-Reply-To: <20100911110050.1c6f275c.rdunlap@xenotime.net>
On 09/11/2010 11:00 AM, Randy Dunlap wrote:
> On Sat, 11 Sep 2010 09:57:23 -0700 Justin P. Mattock wrote:
>
>> finishing up with looking at broken web addresses Im noticing that
>> usr/include/* seems to not work with git i.e. theres a couple of broken
>> addresses in there after changing them, then using git commit -s -a
>> gives me the "nothing to commit message"..
>> why is this?
>
> usr/include/* is all generated files from elsewhere in the kernel tree,
> so you should just change the original files, not the generated ones.
>
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
yeah.. that's what I just realized.. then in this case it's probably
fixed then... as for the rest I went through most of all the
directories(keep in mind only http, didn't check www nor any other
protocol) only a few files in the source tree are left(MAINTAINERS,
etc...) so now the kernel to the most part has working web addresses..
This is what happens when I challenge myself...
Justin P. Mattock
prev parent reply other threads:[~2010-09-11 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 16:57 git crapps out with {kernel_version}/usr/include Justin P. Mattock
2010-09-11 18:00 ` Randy Dunlap
2010-09-11 18:38 ` Justin P. Mattock [this message]
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=4C8BCC98.4070506@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.