From: Andrew Wozniak <awozniak@mc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] When are patches merged to mainline
Date: Tue, 07 Dec 2004 18:04:36 -0500 [thread overview]
Message-ID: <41B63704.2060806@mc.com> (raw)
Hello Wolfgang,
I'm curious about the process for submitted patches and when they appear
in the U-Boot codebase under CVS. I've been merging today's CVS
snapshot with our mods for a custom PPC440 board and found a piece of
missing code. A while back, the patch was submitted to the u-boot-users
list by it does not appear to be in the latest codebase.
The specific patch message is:
From: Travis Sawyer <tsawyer+u-boot@sandburst.com>
To: u-boot-users at lists.sourceforge.net
Subject: [U-Boot-Users] PATCH: update PVR for 440GX Rev C.
Date: Tue, 03 Aug 2004 09:33:53 -0400
I'm a CVS newbee - am I doing something wrong when viewing/downloading
the latest U-Boot codebase? The following was used to download the all
source:
cvs -z3 -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/u-boot u-boot
Thank you for any suggestions.
-Andy
next reply other threads:[~2004-12-07 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 23:04 Andrew Wozniak [this message]
2004-12-07 23:57 ` [U-Boot-Users] When are patches merged to mainline Wolfgang Denk
2004-12-08 14:04 ` Andrew Wozniak
2004-12-14 9:41 ` Detlev Zundel
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=41B63704.2060806@mc.com \
--to=awozniak@mc.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 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.