All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: ptykodi@tykodi.com
Cc: printing-architecture@lists.linux-foundation.org,
	'Printing-japan' <printing-japan@lists.linux-foundation.org>,
	printing-summit@lists.linux-foundation.org
Subject: Re: [Printing-architecture] [Printing-summit] OpenPrinting Summit 2009: Schedules changed onThursday, April 9
Date: Fri, 03 Apr 2009 16:59:51 +0200	[thread overview]
Message-ID: <49D62467.2000309@gmail.com> (raw)
In-Reply-To: <D8967A49BF634D86B35C2069B92D3EC5@TCSLAPTOP01>

Paul Tykodi wrote:
> With the previous proposed schedule, the combination of Thursday
> presentation and potential Friday break-out session, made color printing
> seem like it was being given almost one whole day of effort at the Summit.
> 
> With the new proposed schedule, the effort has dropped below one day and I'm
> waiting to see if that makes a big difference to the customer or not.

Count in also the desktop printing sessions on Thursday afternoon. There 
we will also talk about color management in desktop apps and printing 
dialog.

    Till

  parent reply	other threads:[~2009-04-03 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 16:12 [Printing-architecture] OpenPrinting Summit 2009: Schedules changed on Thursday, April 9 Till Kamppeter
     [not found] ` <B5D52D7F610F471E850981EB156473AD@TCSLAPTOP01>
2009-04-01 16:39   ` [Printing-architecture] [Printing-summit] OpenPrinting Summit 2009: Schedules changed onThursday, " Till Kamppeter
2009-04-01 20:13     ` Hal V. Engel
     [not found]     ` <D8967A49BF634D86B35C2069B92D3EC5@TCSLAPTOP01>
     [not found]       ` <5d88ef650904011059n28cf2d25p5de7abfeafce45b2@mail.gmail.com>
2009-04-01 22:19         ` Till Kamppeter
2009-04-03 14:59       ` Till Kamppeter [this message]
2009-04-01 17:07 ` [Printing-architecture] [Printing-summit] OpenPrinting Summit 2009: Schedules changed on Thursday, " peter sikking
     [not found]   ` <8B8709E6C8B8784583FA9C7C013CB451611930@etd1.etd.ussj.ricoh.com>
2009-04-01 22:35     ` [Printing-architecture] [Printing-summit] OpenPrinting Summit 2009: Schedules changedon " Till Kamppeter
2009-04-02 23:34     ` Till Kamppeter
     [not found]       ` <8B8709E6C8B8784583FA9C7C013CB45161198D@etd1.etd.ussj.ricoh.com>
2009-04-03 19:31         ` Till Kamppeter
     [not found]           ` <8B8709E6C8B8784583FA9C7C013CB4516119DF@etd1.etd.ussj.ricoh.com>
2009-04-06 22:35             ` Till Kamppeter
2009-04-07 17:37               ` Ira McDonald
     [not found]                 ` <8B8709E6C8B8784583FA9C7C013CB451611A07@etd1.etd.ussj.ricoh.com>
2009-04-08 13:01                   ` [Printing-architecture] URGENT: Wiki attachments of the LF stopped working Till Kamppeter
     [not found]                   ` <8B8709E6C8B8784583FA9C7C013CB451611A0D@etd1.etd.ussj.ricoh.com>
2009-04-08 13:17                     ` [Printing-architecture] [Printing-summit] OpenPrinting Summit2009: Schedules changedon Thursday, April 9 Till Kamppeter
2009-04-08 13:03                 ` [Printing-architecture] [Printing-summit] OpenPrinting Summit 2009: " Till Kamppeter

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=49D62467.2000309@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=printing-japan@lists.linux-foundation.org \
    --cc=printing-summit@lists.linux-foundation.org \
    --cc=ptykodi@tykodi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.