From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb@sources.redhat.com, manjo@austin.ibm.com
Subject: Re: mainline vs 6.1 tree
Date: Fri, 16 Apr 2004 03:21:00 -0000 [thread overview]
Message-ID: <20040415180355.B5AC84B104@berman.michael-chastain.com> (raw)
Manjo> I was wondering if the patches/fixes done to mainline tree ever
Manjo> make it into the 6.1 tree? How does it work?
A developer who commits a patch to cvs HEAD might commit it to cvs
gdb_6_1-branch at the same time. Many patches get applied this way
before the release of 6.1. After the release of 6.1, very few patches
get applied this way.
Or, a developer might pick up patches that are already in cvs HEAD
and apply them by hand to gdb_6_1-banch. This is called 'backporting'.
You can look at the ChangeLog files in gdb_6_1-branch
to see how much activity there has been.
Michael C
next reply other threads:[~2004-04-15 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 3:21 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-15 18:04 Manoj Iyer
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=20040415180355.B5AC84B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=gdb@sources.redhat.com \
--cc=manjo@austin.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