public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Avantika Mathur <mathur@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 devel interlock meeting minutes (March 14, 2007)
Date: Fri, 16 Mar 2007 09:31:35 -0700	[thread overview]
Message-ID: <20070316093135.174b4b69.rdunlap@xenotime.net> (raw)
In-Reply-To: <45F87C03.506@linux.vnet.ibm.com>

On Wed, 14 Mar 2007 15:49:39 -0700 Avantika Mathur wrote:

> Ext4 Developer Interlock Call: 03/14/2007 Meeting Minutes
> 
> Attendees: Mingming Cao, Eric Sandeen, Ted Ts'o, Dave Kleikamp, Suparna Bhattacharya, Takashi Sato, Avantika Mathur
> 
> Minutes can be accessed at: http://ext4.wiki.kernel.org/index.php/Ext4_Developer%27s_Conference_Call 
> 
> 
> Ext4 git Tree:
> 
> - Shaggy and Eric fixed the recent problems with the nanosecond timestamps in the git tree
> 
> - There is a general problem that the git tree is not updated frequently
> 
> 	- Ted feels there is not enough testing done to feel comfortable updating to a new release
> 
>         -- Many of the patches added to the tree are not tested properly.  
> 	-- It would be helpful if people could pick up the tree and test it, and make sure all upstream merging criteria is met by ext4 developers.
> 
>     - Currently looking at methods of automating testing of each new git tree release on different architectures and benchmarks.
> 
>     - Slow code review is also slowing down ext4.
> 
> - Ted suggested maintaining a git tree that tracks the patch queue, so there can be multiple people working on the patch queue. 
> 	- When patches are stable, update the central git tree that can then be pushed upstream.
> 
> - Ted will start a second git tree, and initially put Shaggy and Mingming as additional users who can access the tree. 

Hi,
What's the purpose of this second git tree, please?

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      parent reply	other threads:[~2007-03-16 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 22:49 Ext4 devel interlock meeting minutes (March 14, 2007) Avantika Mathur
2007-03-14 22:51 ` Mingming Cao
2007-03-16 16:31 ` Randy Dunlap [this message]

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=20070316093135.174b4b69.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mathur@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox