kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (Nick Krause)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Help with git
Date: Fri, 8 Aug 2014 14:18:50 -0400	[thread overview]
Message-ID: <CAPDOMVjzNJJQpT+nZD-=Fs5Op2DwAyiEHpf3Br-QKyb+RP0ymA@mail.gmail.com> (raw)
In-Reply-To: <CAGpXXZL7iuKGRH50tu6bMq6Ju2EfrruDOH_1H3Hoy=Aej6YHdQ@mail.gmail.com>

On Fri, Aug 8, 2014 at 2:07 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
> On Fri, Aug 8, 2014 at 1:37 PM, Nick Krause <xerofoify@gmail.com> 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 participating here and prove yourself.
>
> Also, staging clean-ups that are just beautification are not really
> needed in staging.
>
> Greg KH has automated scripts he could run to clean it all up in one
> whack.  I assume he chooses not to let newbies have the practice.
>
> That means every time he accepts a beautification patch he is doing
> extra work for the benefit of the submitter, not for the benefit of
> staging.
>
> So at this point, don't think about beautification work.  If you want
> someone to submit a patch for you, it needs to be a patch that
> actually fixes a bug.
>
> Greg
>
>
>
> --
> Greg Freemyer

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.
Cheers Nick

  parent reply	other threads:[~2014-08-08 18:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  1:48 Help with git Nick Krause
2014-08-08  1:52 ` Kristofer Hallin
2014-08-08  1:58   ` Nick Krause
2014-08-08  1:59     ` Nick Krause
2014-08-08  2:00 ` Valdis.Kletnieks at vt.edu
2014-08-08  2:01   ` Nick Krause
2014-08-08  2:18     ` Sudip Mukherjee
2014-08-08  2:25       ` Nick Krause
2014-08-08  3:03         ` Valdis.Kletnieks at vt.edu
2014-08-08  3:05         ` Valdis.Kletnieks at vt.edu
2014-08-08  3:13           ` Nick Krause
2014-08-08 17:04             ` Nick Krause
2014-08-08 17:30               ` Nuno Martins
2014-08-08 17:37                 ` Nick Krause
2014-08-08 18:07                   ` Greg Freemyer
2014-08-08 18:16                     ` Kristofer Hallin
2014-08-08 18:28                       ` Robert P. J. Day
2014-08-08 18:31                         ` Kristofer Hallin
2014-08-08 18:18                     ` Nick Krause [this message]
2014-08-08 18:28                       ` Valdis.Kletnieks at vt.edu
2014-08-08 18:26                   ` Valdis.Kletnieks at vt.edu
2014-08-08 17:39               ` Valdis.Kletnieks at vt.edu
2014-08-08 17:53                 ` Nick Krause
2014-08-08 18:25                   ` Valdis.Kletnieks at vt.edu
2014-08-08 20:28                     ` Formula One Scheduler (was Re: Help with git) Arlie Stephens
2014-08-08 20:46                       ` Nick Krause
2014-08-09  5:23                         ` Sudip Mukherjee
2014-08-09 12:43                           ` Lidza Louina
2014-08-09  0:17                       ` Valdis.Kletnieks at vt.edu
2014-08-09 13:01                         ` Philipp Muhoray

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='CAPDOMVjzNJJQpT+nZD-=Fs5Op2DwAyiEHpf3Br-QKyb+RP0ymA@mail.gmail.com' \
    --to=xerofoify@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).