From: Konrad Eisele <konrad@gaisler.com>
To: sparclinux@vger.kernel.org
Subject: Re: LEON SPARC git repository
Date: Fri, 05 Jun 2009 09:40:04 +0000 [thread overview]
Message-ID: <4A28E7F4.3020209@gaisler.com> (raw)
In-Reply-To: <4A27926C.5010501@gaisler.com>
Hi Sam,
> If you want this reviewed then please do as asked and send a set of individual mails
> each containing one logical change - with a description what it contains.
> I (and others too) do not go hunting to find patches to review.
Ok, I can do this (next week). This would be 20 mails for 20 files. Is everybody on the
list ok with it?
>>From the list below I can see you have a logical split of the changes.
> So you just have to add the corresponding patch too.
>
> If you did this before than document what was changed since then, which
> review comments was addressed and especially which was not (and why).
Didnt understand this. There was nothing sent previously.
> So please inline patches - with good changelogs.
Ok, I'll send them next.
I'm not familiar with how patches get applied. Can someone describe
who actually is checking in a patch so that it appears in the final kernel?
Is it you (Sam)?
Is this patch sending only a "review" or do they get checked in afterwards?
If it is only a "review" who is then the one that actually checks them in?
-- Greetings Konrad
>
> Sam
>
>
next prev parent reply other threads:[~2009-06-05 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 9:22 LEON SPARC git repository Kristoffer Glembo
2009-06-04 18:11 ` Sam Ravnborg
2009-06-05 8:39 ` Konrad Eisele
2009-06-05 9:19 ` Sam Ravnborg
2009-06-05 9:40 ` Konrad Eisele [this message]
2009-06-05 9:55 ` Sam Ravnborg
2009-06-05 9:57 ` Konrad Eisele
2009-06-06 7:11 ` Sam Ravnborg
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=4A28E7F4.3020209@gaisler.com \
--to=konrad@gaisler.com \
--cc=sparclinux@vger.kernel.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.