public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request u-boot-blackfin.git (post branch)
Date: Tue, 5 Jul 2011 18:12:44 -0400	[thread overview]
Message-ID: <201107051812.45342.vapier@gentoo.org> (raw)
In-Reply-To: <20110705215432.8A7841579E12@gemini.denx.de>

On Tuesday, July 05, 2011 17:54:32 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > > Your bogus repostings are rejected, not the original patches.
> > 
> > so since my pull requests are actually the original patches, i can go
> > ahead and change them from "rejected" to "new" ?  or should i just send
> > new pull requests ?
> 
> This has already been answered.  You are wasting my time.  Stop it,
> now.

your logic makes no sense.  you say you are fine with the original patches, 
but i cant send pull requests of the original patches.  i guess i'll have to 
wait for you to pick the individual patches out of patchwork then.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20110705/ef31a932/attachment.pgp 

  reply	other threads:[~2011-07-05 22:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 19:26 [U-Boot] Pull request u-boot-blackfin.git (post branch) Mike Frysinger
2011-06-28 19:26 ` [U-Boot] [PATCH 1/5] post: fix up I/O helper usage Mike Frysinger
2011-06-28 19:26   ` [U-Boot] [PATCH 2/5] post: add gpio hotkey support Mike Frysinger
2011-06-28 19:26   ` [U-Boot] [PATCH 3/5] post: use ARRAY_SIZE Mike Frysinger
2011-06-28 19:26   ` [U-Boot] [PATCH 4/5] post: new nor flash test Mike Frysinger
2011-06-28 19:26   ` [U-Boot] [PATCH 5/5] serial: implement common uart post test Mike Frysinger
2011-06-29 21:21 ` [U-Boot] Pull request u-boot-blackfin.git (post branch) Wolfgang Denk
2011-06-29 23:30   ` Mike Frysinger
2011-06-30 10:29     ` Wolfgang Denk
2011-06-30 15:26       ` Mike Frysinger
2011-06-30 15:38         ` Wolfgang Denk
2011-06-30 15:42           ` Mike Frysinger
2011-06-30 15:49             ` Wolfgang Denk
2011-06-30 16:04               ` Mike Frysinger
2011-06-30 21:10                 ` Wolfgang Denk
2011-06-30 21:12                   ` Mike Frysinger
2011-06-30 22:57                     ` Wolfgang Denk
2011-06-30 23:06                       ` Mike Frysinger
2011-07-01  4:36                         ` Wolfgang Denk
2011-07-01 23:27                           ` Mike Frysinger
2011-07-03 22:30                             ` Wolfgang Denk
2011-07-05  1:25                               ` Mike Frysinger
2011-07-05  4:42                                 ` Wolfgang Denk
2011-07-05  6:14                                   ` Mike Frysinger
2011-07-05  9:59                                     ` Wolfgang Denk
2011-07-05 17:32                                       ` Mike Frysinger
2011-07-05 21:54                                         ` Wolfgang Denk
2011-07-05 22:12                                           ` Mike Frysinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-09-29 22:28 Mike Frysinger
2011-10-01 19:43 ` Wolfgang Denk

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=201107051812.45342.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=u-boot@lists.denx.de \
    /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