On Fri, 8 Aug 2014, Kristofer Hallin wrote:
> This list is now discussing Nick's problems all the time and nothing
> else.
more specifically, the list is now teaching nick how to use git. so,
on that note, i'm unsubscribing until this idiocy goes away. catch you
on the flip side, as they say.
Am 2014-08-09 02:17, schrieb valdis.kletni...@vt.edu:
On Fri, 08 Aug 2014 13:28:45 -0700, Arlie Stephens said:
On Aug 08 2014, valdis.kletni...@vt.edu wrote:
There's a big difference between knowing how to change the spark plugs on
a VW Beetle, and being able to walk into a Formula One pit and
Nick, if you get accepted in a program like google summer of code, you will
get a mentor (that's how I got started). I don't know the odds of that
happening because you don't have a good reputation in the kernel. Look for
a program like gsoc and apply.
Another option is looking for someone in real
On Sat, Aug 9, 2014 at 2:16 AM, Nick Krause wrote:
> On Fri, Aug 8, 2014 at 4:28 PM, Arlie Stephens wrote:
>> On Aug 08 2014, valdis.kletni...@vt.edu wrote:
>>> There's a big difference between knowing how to change the spark plugs on
>>> a VW Beetle, and being able to walk into a Formula One pit
On Fri, 08 Aug 2014 13:28:45 -0700, Arlie Stephens said:
> On Aug 08 2014, valdis.kletni...@vt.edu wrote:
> > There's a big difference between knowing how to change the spark plugs on
> > a VW Beetle, and being able to walk into a Formula One pit and make tuning
> > suggestions that actually help t
On Fri, Aug 8, 2014 at 4:28 PM, Arlie Stephens wrote:
> On Aug 08 2014, valdis.kletni...@vt.edu wrote:
>> There's a big difference between knowing how to change the spark plugs on
>> a VW Beetle, and being able to walk into a Formula One pit and make tuning
>> suggestions that actually help the pe
On Aug 08 2014, valdis.kletni...@vt.edu wrote:
> There's a big difference between knowing how to change the spark plugs on
> a VW Beetle, and being able to walk into a Formula One pit and make tuning
> suggestions that actually help the performance.
>
> And yes, there's *that* big a gap between th
Thinking about the same thing. This list is not interesting any more.
On 8 Aug 2014 20:28, "Robert P. J. Day" wrote:
> On Fri, 8 Aug 2014, Kristofer Hallin wrote:
>
> > This list is now discussing Nick's problems all the time and nothing
> > else.
>
> more specifically, the list is now teaching
On Fri, 08 Aug 2014 14:18:50 -0400, Nick Krause said:
> Thanks for the notice , if there are any bugs that are simple for a
> newbie on Linus's tree I would be glad to help out there.
This isn't the kernel it was 8 or 10 years ago. There's not a lot of
low-hanging fruit left - that's why the ker
On Fri, 08 Aug 2014 13:37:25 -0400, Nick Krause said:
> Would you mind asking Greg if he wants some help with staging clean up
> as he is very upset with me after me
> not listening and I own it to him to help help him out.
No, what you owe him is to *SHUT THE HELL UP* and *DONT DO IT AGAIN*
unti
On Fri, 08 Aug 2014 13:53:50 -0400, Nick Krause said:
> Then I am going to work on a few areas( still deciding where to specialize)
> 1. Btrfs
> 2. Scheduler
> 3. F2FS
> 4. Networking
> 5. Drivers(mostly USB and Intel Graphics)
Pick *one* thing. There's quite obviously a wide gap between your le
On Fri, Aug 8, 2014 at 2:07 PM, Greg Freemyer wrote:
> On Fri, Aug 8, 2014 at 1:37 PM, Nick Krause wrote:
>> Thanks Numo,
>> Would you mind asking Greg if he wants some help with staging clean up
>> as he is very upset with me after me
>> not listening and I own it to him to help help him out.
>>
But still, the best thing for Nick to do is to stay away from patches,
bugs, staging and whatnot for a long time. Try to learn before even
considering sending patches.
You are on the same track as before, you are trying to figure out how to
send patches even if a lot of people have told you not to
On Fri, Aug 8, 2014 at 1:37 PM, Nick Krause wrote:
> Thanks Numo,
> Would you mind asking Greg if he wants some help with staging clean up
> as he is very upset with me after me
> not listening and I own it to him to help help him out.
> Cheers Nick
Greg KH monitors kernelnewbies.
Keep participa
On Fri, Aug 8, 2014 at 1:39 PM, wrote:
> On Fri, 08 Aug 2014 13:04:15 -0400, Nick Krause said:
>
>> 1.git branch next
>
> No, this should be (3) or so. You really want to 'git clone' linus's tree and
> then 'git remote add' the linux-next tree before you do this.
>
> If you're new to git, do you
On Fri, 08 Aug 2014 13:04:15 -0400, Nick Krause said:
> 1.git branch next
No, this should be (3) or so. You really want to 'git clone' linus's tree and
then 'git remote add' the linux-next tree before you do this.
If you're new to git, do yourself a favor, follow the directions, and just
build
On Fri, Aug 8, 2014 at 1:30 PM, Nuno Martins wrote:
>
>
>
> On Fri, Aug 8, 2014 at 6:04 PM, Nick Krause wrote:
>>
>> On Thu, Aug 7, 2014 at 11:13 PM, Nick Krause wrote:
>> > On Thu, Aug 7, 2014 at 11:05 PM, wrote:
>> >> On Thu, 07 Aug 2014 22:25:06 -0400, Nick Krause said:
>> >>
>> >>> 1. git
On Fri, Aug 8, 2014 at 6:04 PM, Nick Krause wrote:
> On Thu, Aug 7, 2014 at 11:13 PM, Nick Krause wrote:
> > On Thu, Aug 7, 2014 at 11:05 PM, wrote:
> >> On Thu, 07 Aug 2014 22:25:06 -0400, Nick Krause said:
> >>
> >>> 1. git clone linux-next
> >>
> >> Before you do the git add, you *really* w
On Thu, Aug 7, 2014 at 11:13 PM, Nick Krause wrote:
> On Thu, Aug 7, 2014 at 11:05 PM, wrote:
>> On Thu, 07 Aug 2014 22:25:06 -0400, Nick Krause said:
>>
>>> 1. git clone linux-next
>>
>> Before you do the git add, you *really* want to create a branch for
>> yourself to work on.
>>
>>> 2. git ad
On Thu, Aug 7, 2014 at 11:05 PM, wrote:
> On Thu, 07 Aug 2014 22:25:06 -0400, Nick Krause said:
>
>> 1. git clone linux-next
>
> Before you do the git add, you *really* want to create a branch for
> yourself to work on.
>
>> 2. git add file changed
>
> Because otherwise this will get dumped on on
On Thu, 07 Aug 2014 22:25:06 -0400, Nick Krause said:
> 1. git clone linux-next
Before you do the git add, you *really* want to create a branch for
yourself to work on.
> 2. git add file changed
Because otherwise this will get dumped on one of 200+ linux-next branches
and cause acute indigestio
On Thu, 07 Aug 2014 22:25:06 -0400, Nick Krause said:
> 1. git clone linux-next
Don't do that. You'll get something that you can't easily update.
git clone linux *LINUS MAINLINE TREE*
git remote add linux-next *add this as a remote*
git fetch --all
then use git remote up to update
On Thu, Aug 7, 2014 at 10:18 PM, Sudip Mukherjee
wrote:
>
> On Aug 8, 2014 7:32 AM, "Nick Krause" wrote:
>>
>> On Thu, Aug 7, 2014 at 10:00 PM, wrote:
>> > On Thu, 07 Aug 2014 21:48:54 -0400, Nick Krause said:
>> >
>> >> sed: can't read /home/nick/linux-next/.git/rebase-apply/info: No such
>> >
On Aug 8, 2014 7:32 AM, "Nick Krause" wrote:
>
> On Thu, Aug 7, 2014 at 10:00 PM, wrote:
> > On Thu, 07 Aug 2014 21:48:54 -0400, Nick Krause said:
> >
> >> sed: can't read /home/nick/linux-next/.git/rebase-apply/info: No such
> >> file or directory
> >
> > It usually helps if you give the actual
On Thu, Aug 7, 2014 at 10:00 PM, wrote:
> On Thu, 07 Aug 2014 21:48:54 -0400, Nick Krause said:
>
>> sed: can't read /home/nick/linux-next/.git/rebase-apply/info: No such
>> file or directory
>
> It usually helps if you give the actual command that you were trying to do.
>
> You didn't do this on
On Thu, 07 Aug 2014 21:48:54 -0400, Nick Krause said:
> sed: can't read /home/nick/linux-next/.git/rebase-apply/info: No such
> file or directory
It usually helps if you give the actual command that you were trying to do.
You didn't do this on top of a linux-next tree that you did a 'git pull' t
On Thu, Aug 7, 2014 at 9:58 PM, Nick Krause wrote:
> On Thu, Aug 7, 2014 at 9:52 PM, Kristofer Hallin
> wrote:
>> Seems like something is messed up. Try 'git rebase --abort' and see if
>> that helps you.
>>
>> And don't try to get that patch merged upstream.
>>
>> On Fri, Aug 8, 2014 at 3:48 AM,
On Thu, Aug 7, 2014 at 9:52 PM, Kristofer Hallin
wrote:
> Seems like something is messed up. Try 'git rebase --abort' and see if
> that helps you.
>
> And don't try to get that patch merged upstream.
>
> On Fri, Aug 8, 2014 at 3:48 AM, Nick Krause wrote:
>> I can't seem to apply one of my created
Seems like something is messed up. Try 'git rebase --abort' and see if
that helps you.
And don't try to get that patch merged upstream.
On Fri, Aug 8, 2014 at 3:48 AM, Nick Krause wrote:
> I can't seem to apply one of my created patches after trying for the last
> hour.
> This is what is poppin
I can't seem to apply one of my created patches after trying for the last hour.
This is what is popping up, if anybody can tell me is wrong that would be great.
sed: can't read /home/nick/linux-next/.git/rebase-apply/info: No such
file or directory
sed: can't read /home/nick/linux-next/.git/rebase-
30 matches
Mail list logo
