linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Ricardo Scop <scop@digitel.com.br>
Cc: Andrew Johnson <anj@aps.anl.gov>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: BK to CVS?
Date: Fri, 05 Oct 2001 22:25:22 -0400	[thread overview]
Message-ID: <3BBE6B92.60497E1@mvista.com> (raw)
In-Reply-To: 01100519044401.01029@scop.digitel.com.br


Ricardo Scop wrote:

> We internally use CVS nowadays, therefore I'm very interested in your
> standard procedures to manage externally developed code.

I would appreciate a patch against the current linuxppc_2_4_devel
tree.  Please pull the latest tree, do your work in that tree, and
then generate a patch using one of the convenient bk commands that
I hope Tom Rini can suggest :-).

It's quite time consuming to get patches that are "almost" up to
date and having to manually sort out the differences.  I could spend
24 hours a day just applying and testing patches sent to my personal
e-mail addresses.  It _really_ helps when they are up to date :-).

Thanks.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-10-06  2:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 17:05 BK to CVS? Kent Borg
2001-10-03 18:32 ` Tom Rini
2001-10-04 13:25   ` Kent Borg
2001-10-04 20:29     ` Tom Rini
2001-10-05 15:11       ` Kent Borg
2001-10-05 15:48         ` Andrew Johnson
2001-10-05 16:04           ` Ricardo Scop
2001-10-06  2:25             ` Dan Malek [this message]
2001-10-05 20:52               ` BK to CVS? + MDIO Ricardo Scop
2001-10-06  3:34                 ` Tom Rini
2001-10-06  3:42                   ` Re[2]: " Ricardo Scop
2001-10-06  3:41                 ` Dan Malek
2001-10-08 12:01                 ` Jerry Van Baren
2001-10-08 13:06                   ` Wolfgang Denk
2001-10-06  2:43               ` BK to CVS? Tom Rini
2001-10-05 16:23           ` Kent Borg
2001-10-05 16:42             ` Andrew Johnson

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=3BBE6B92.60497E1@mvista.com \
    --to=dan@mvista.com \
    --cc=anj@aps.anl.gov \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=scop@digitel.com.br \
    /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).