From: Coly Li <coyli@suse.de>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-ext4@vger.kernel.org
Subject: Re: question about patch queue and ext4-git
Date: Mon, 15 Oct 2007 20:46:32 +0800 [thread overview]
Message-ID: <47136128.5050301@suse.de> (raw)
In-Reply-To: <20071015051005.0865b2a7@gara>
Thanks for the replying :-)
Jose R. Santos wrote:
> On Mon, 15 Oct 2007 13:36:05 +0800
> Coly Li <coyli@suse.de> wrote:
>
>> Now in my mind there are several words for ext4 patches, most frequently one are "patch queue".
>>
>> I see the patches in patch queue from
>> http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/LATEST/broken-out/ .
>> Also I confirm some of the patches are in ext4 git tree now, but I am not sure for two questions:
>> 1) Whether all the patches are in ext4 git tree ?
>
> Yes, all these patches should be in ext4 git tree.
>
>> 2) This patch queue is only used to push ext4 patch into upstream ?
>
> The patch queue series is divided into stable and unstable patches.
> The stable patches are the one usually the ones used to push back
> upstream, while the unstable section has the patches for development
> purposes only and are not ready for pushing upstream (and some may
> never make it in).
How to recognize which patch is stable patch and which one is unstable patch ?
>
>> Also there is a patch-queue git at http://repo.or.cz/w/ext4-patch-queue.git , is it same to the
>> patches in http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/ ?
>
> Same thing bug in git format. I believe Ted updates his patch queue
> from the patches in the git tree repo, so if you want latest/greatest
> the git tree is what you want.
>
>> Thanks for clarifying :-)
>>
>>
>
> -JRS
--
Coly Li
SuSE PRC Labs
next prev parent reply other threads:[~2007-10-15 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 5:36 question about patch queue and ext4-git Coly Li
2007-10-15 10:10 ` Jose R. Santos
2007-10-15 12:46 ` Coly Li [this message]
2007-10-15 13:21 ` Jose R. Santos
2007-10-15 14:29 ` Coly Li
2007-10-15 21:59 ` Mingming Cao
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=47136128.5050301@suse.de \
--to=coyli@suse.de \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).