From: Tobias Klauser <tklauser@nuerscht.ch>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] One question
Date: Sat, 23 Apr 2005 14:29:27 +0000 [thread overview]
Message-ID: <20050423142927.GA839@neon> (raw)
In-Reply-To: <20050422081037.GA31439@rhum.iomeda.fr>
[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]
On Fri, Apr 22, 2005 at 10:10:38AM +0200, Christophe Lucas wrote:
> I ask me one question and I don't have any correct answer:
> Could it be made one tool to follow progress about long series of patch
> about one entry in KJ TODO ?
Generally this is a good idea. Otherwise this puts a lot of work onto
the KJ maintainer and I'm not sure if he is willing to accept that
additional work.
> Such as :
> .*set_dma_mask patch series
>
> Some person have made lot of great job on this, but we don't know what
> is pending, what is rejected.
Yup, some maintainers are very good at letting you know about
accepting/rejecting patches, others are not.
> I know, I can read all archive of KJ ML, thanks :-)
That's what they are for. ;-)
> I have tough about one solution, but it is not efficient and correct:
>
> ./linux-x.y.z-suffix/
> ./linux-x.y.z-suffix/patch-serie/
> ./linux-x.y.z-suffix/patch-serie/merged/
> ./linux-x.y.z-suffix/patch-serie/pending/ (commited here)
> ./linux-x.y.z-suffix/patch-serie/merged/
>
> The problem is : ./linux-x.y.z-suffix/
Exactly. I don't think such a approach will help anyone, kernel versions
just change too often. And, as mentioned above it puts a lot of work
onto the maintainer.
> We do the job again and again...
Hmmm, most of the time we do not need to start again, we just have to
adjust the patches. KJ patches are often not very intrusive and do not
change many lines of code, so this is generally easy.
> So perhaps this mail is a waste of your time, so sorry.
No, it isn't. Ideas/discussion on how to improve work on an issue is
always good.
Tobias
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-04-23 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 8:10 [KJ] One question Christophe Lucas
2005-04-22 8:29 ` Christophe Lucas
2005-04-22 14:03 ` Domen Puncer
2005-04-22 14:32 ` Christophe Lucas
2005-04-23 14:29 ` Tobias Klauser [this message]
2005-04-24 9:36 ` Christophe Lucas
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=20050423142927.GA839@neon \
--to=tklauser@nuerscht.ch \
--cc=kernel-janitors@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.