public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Mikkel Krautz <krautz@gmail.com>
Cc: linux-kernel@vger.kernel.org, roms@lpg.ticalc.org, jb@technologeek.org
Subject: Re: [PATCH 0/3] TIGLUSB Cleanups
Date: Wed, 26 Jan 2005 09:17:18 -0800	[thread overview]
Message-ID: <20050126171718.GA3853@kroah.com> (raw)
In-Reply-To: <d4b385205012609012951e0dd@mail.gmail.com>

On Wed, Jan 26, 2005 at 06:01:28PM +0100, Mikkel Krautz wrote:
> On Wed, 26 Jan 2005 08:57:07 -0800, Greg KH <greg@kroah.com> wrote:
> > On Wed, Jan 26, 2005 at 05:48:19PM +0100, Mikkel Krautz wrote:
> > > On Wed, 26 Jan 2005 08:40:10 -0800, Greg KH <greg@kroah.com> wrote:
> > > >
> > > > Use a different email client, or attach the patches as plain text.
> > > >
> > > > Good luck,
> > > >
> > > > greg k-h
> > > >
> > >
> > > Alright, they're attached this time.
> > > I hope this'll do for now. :-)
> > 
> > Nope, please break them out into the three pieces, in three different
> > emails like you did before so I can apply them all properly.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> 
> Should I add "[RESEND]" or something simmilar to the subjects, so they
> can be easily distinguished from the original ones?

Nah, just send them again, I can distinguish them by the fact that they
can actually be applied :)

thanks,

greg k-h

  reply	other threads:[~2005-01-27  3:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-26 16:48 [PATCH 0/3] TIGLUSB Cleanups Mikkel Krautz
2005-01-26 16:57 ` Greg KH
2005-01-26 17:01   ` Mikkel Krautz
2005-01-26 17:17     ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-26 16:04 Mikkel Krautz
2005-01-26 16:27 ` Mikkel Krautz
2005-01-26 16:40   ` Greg KH

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=20050126171718.GA3853@kroah.com \
    --to=greg@kroah.com \
    --cc=jb@technologeek.org \
    --cc=krautz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roms@lpg.ticalc.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