All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ohly <Patrick.Ohly@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: A question of workflow
Date: Sun, 07 Jan 2007 22:40:50 +0100	[thread overview]
Message-ID: <1168206051.18289.14.camel@ip6-localhost> (raw)
In-Reply-To: <1662139633.20070107231632@gmail.com>

On So, 2007-01-07 at 23:16 +0200, Paul Sokolovsky wrote:
> Hello Patrick,
> > What do you think? Did I miss something?
> 
>   Well, why would OE core developers (err, what about non-core
> developers - we also care for contributed patches - after all, to get
> commit access to OE, you first contribute bunch of patches) - well, why
> would they do that?

Perhaps because they care enough about external contributions to make
life easier for the people preparing patches? The fact that their own
changes would also be tracked by monotone is probably less important.

I'm aware that this is not something that can be requested from
volunteers, but at least it can be suggested and perhaps someone will
find it useful and (more important) doable.

> Just in case, there's always another alternative - contributors
> just should submit patches in the perfect form, suitable for merging w/o
> tweaks.

I'm not so sure that this will work - As Koen said, having to tweak a
patch is the rule, not the exception. Just doing those tweaks instead of
striving for perfect patches might be less work also for the core
developers.

>  Obviously, it's just the same not attainable, nor it's really
> *that* important - we want people contribute more than either us or them
> to follow strict rules.

Of course, these shouldn't be strict rules, but having some guidelines
wouldn't hurt either. I think I have seen questions about "how to
contribute patches" several times on this list already.

-- 
Bye, Patrick Ohly
--  
Patrick.Ohly@gmx.de
http://www.estamos.de/



  reply	other threads:[~2007-01-07 21:43 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-30  5:16 A question of workflow Matthew Palmer
2006-12-30 19:19 ` Richard Purdie
2006-12-30 21:43   ` Matthew Palmer
2006-12-30 22:07     ` Koen Kooi
2006-12-30 23:08       ` Erik Hovland
2006-12-30 23:40         ` Matthew Palmer
2006-12-31  0:02           ` Richard Purdie
2006-12-31  9:36         ` Koen Kooi
2006-12-31 11:12           ` Matthew Palmer
2006-12-30 23:59       ` Matthew Palmer
2006-12-31  0:06         ` Richard Purdie
2006-12-31  9:45           ` Koen Kooi
2006-12-31 11:00             ` Matthew Palmer
2006-12-31 11:10               ` Koen Kooi
2007-01-07 20:04             ` Patrick Ohly
2007-01-07 21:16               ` Paul Sokolovsky
2007-01-07 21:40                 ` Patrick Ohly [this message]
2007-01-07 22:03                 ` Matthew Palmer
2007-01-07 22:46                   ` Justin Patrin
2007-01-07 22:56                     ` Matthew Palmer
2007-01-07 23:11                       ` Justin Patrin
2007-01-08 18:28                     ` Patrick Ohly
2007-01-08 19:11                       ` Justin Patrin
2007-01-08 21:02                         ` Patrick Ohly
2007-01-08 21:13                           ` Koen Kooi
2007-01-08 21:43                             ` Patrick Ohly
2007-01-08 21:53                             ` Justin Patrin
2007-01-09  9:42                               ` Richard Purdie
2007-01-09 19:51                                 ` Patrick Ohly
2007-01-08  1:18                   ` Rolf Leggewie
2007-01-08 18:09                     ` Patrick Ohly
2007-01-09 12:51                       ` Rolf Leggewie
2007-01-09 12:54                       ` Rolf Leggewie
2007-01-09 19:39                         ` Patrick Ohly
2007-01-02 20:06       ` Paul Sokolovsky
2007-01-02 20:08         ` [Angstrom-devel] " Koen Kooi
2007-01-04  4:23         ` Justin Patrin
2006-12-31  2:41   ` jack-oe
2007-01-02  0:05 ` Cliff Brake

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=1168206051.18289.14.camel@ip6-localhost \
    --to=patrick.ohly@gmx.de \
    --cc=openembedded-devel@lists.openembedded.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 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.