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: Thu, 7 Aug 2014 21:58:00 -0400	[thread overview]
Message-ID: <CAPDOMVi7YMWu08zSmdhZTgyfUVrL-ROpfZv69F0OixcmZ4KqGg@mail.gmail.com> (raw)
In-Reply-To: <CAAXLKtSuh6RsGFEVc0C1-C_bEm2pgROAWOTkLp9OD3Fz0tYRvg@mail.gmail.com>

On Thu, Aug 7, 2014 at 9:52 PM, Kristofer Hallin
<kristofer.hallin@gmail.com> 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 <xerofoify@gmail.com> wrote:
>> 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-apply/info: No such
>> file or directory
>> sed: can't read /home/nick/linux-next/.git/rebase-apply/info: No such
>> file or directory
>> Patch does not have a valid e-mail address.
>> Nick
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

That was fast, thanks I will try that see if works. I am banned from
the LKML for now,
just telling you up front so you will have to send it in for me, let's
just state I was not
listening. :)
Nick
P.S. Listening to The Wall seems to great for listening to well programming.

  reply	other threads:[~2014-08-08  1:58 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 [this message]
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
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=CAPDOMVi7YMWu08zSmdhZTgyfUVrL-ROpfZv69F0OixcmZ4KqGg@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).