From: Richard Danter <richard.danter@ntlworld.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-Boot Developer's Information
Date: Tue, 16 Aug 2005 09:50:03 +0100 [thread overview]
Message-ID: <4301A8BB.3000309@ntlworld.com> (raw)
In-Reply-To: <20050816001516.11FBA353CEB@atlas.denx.de>
Wolfgang Denk wrote:
> Hello everybody.
>
> the number of contributions to the U-Boot project has been
> continuously growing, and for some time I've been looking for more
> efficient ways to deal with all the patches and submissions. The
> current development cycle with a central CVS repository at
> SourceForge has a couple of problems:
...
How do these changes effect patches already submitted but not yet
applied? Is there anything we need to do to help speed up the process of
getting patches in?
Thanks
Rich
next prev parent reply other threads:[~2005-08-16 8:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 0:15 [U-Boot-Users] U-Boot Developer's Information Wolfgang Denk
2005-08-16 3:35 ` glikely at gmail.com
2005-08-16 7:29 ` Wolfgang Denk
2005-08-16 8:50 ` Richard Danter [this message]
2005-08-16 15:56 ` Wolfgang Denk
2005-08-16 10:00 ` [U-Boot-Users] " Catalin Marinas
2005-08-16 15:59 ` Wolfgang Denk
2005-08-16 16:22 ` Catalin Marinas
2005-08-16 12:31 ` [U-Boot-Users] " Brian Waite
2005-08-16 21:53 ` Wolfgang Denk
2005-08-17 10:31 ` Detlef Vollmann
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=4301A8BB.3000309@ntlworld.com \
--to=richard.danter@ntlworld.com \
--cc=u-boot@lists.denx.de \
/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