public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Revision COntrol, Patch Database -- was: Patch for Cirrus Logic EDB9312
Date: Tue, 18 Jan 2005 11:01:52 -0500	[thread overview]
Message-ID: <41ED32F0.3020109@smiths-aerospace.com> (raw)
In-Reply-To: <20050118092849.952C3C108D@atlas.denx.de>

Wolfgang Denk wrote:
> In message <6.0.1.1.0.20050118091601.01ba8630@192.168.2.1> you wrote:
> 
>>Generally speaking about patch management, have you ever thought about
>>using BitKeeper to manage U-Boot repository? Thanks to your great effort and
> 
> 
> No. U-Boot is a Free Software project, and  we  will  never  make  it
> dependent on a proprietary product withj nsty licensing terms.
> 
> 
>>to the U-Boot developers, its popularity is growing very fast and I think that
>>patch management task is become really huge. I started working with BitKeeper
>>because Linux 2.6 and I think it could ease this task a lot.
> 
> 
> It could if it was usable. But it ain't. It restricts your freedom in
> an unacceptable way. Did you read the BKL license? [It's difficult to
> do because it's only readable AFTER installing the product.] Did  you
> read  for example section "3. LICENSEE OBLIGATIONS": "(d) No free use
> for competitors". What if I happen to hack CVS, subversion or arch or
> any other free frevision control system?
> 
> 
> But I am perfectly aware that a system with support  for  distributed
> repositories  would  be beneficial. We will probably try switching to
> arch.
> 
> 
> And while we are at it: another thing that would be useful is a patch
> database. Any suggestions?
> 
> 
> Best regards,
> 
> Wolfgang Denk
> 

The obvious answer (but not necessarily the correct answer :-) is gforge
   http://gforge.org/
It says it can use subversion for version control as well as cvs.  That 
doesn't get you your distributed repository, however it does make it an 
easier switch.

gvb

  parent reply	other threads:[~2005-01-18 16:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4120DD8B.8040709@imc-berlin.de>
2004-10-09 22:20 ` [U-Boot-Users] Re: [PATCH] Cleanup cpu/arm920t using SoC Wolfgang Denk
2004-10-12 14:02   ` [U-Boot-Users] Patch for Cirrus Logic EDB9312 llandre
2005-01-09 23:43     ` Wolfgang Denk
2005-01-18  8:32       ` llandre
2005-01-18  9:28         ` [U-Boot-Users] Revision COntrol, Patch Database -- was: " Wolfgang Denk
2005-01-18  9:59           ` [U-Boot-Users] " llandre
2005-01-18 16:01           ` Jerry Van Baren [this message]
2005-01-18 21:13             ` [U-Boot-Users] " Wolfgang Denk
2005-01-18 22:49               ` [U-Boot-Users] Revision COntrol, Patch Database Jerry Van Baren
2005-01-21 17:42                 ` llandre
2005-01-19 10:28               ` [U-Boot-Users] Re: Revision COntrol, Patch Database -- was: Patch for Cirrus Logic EDB9312 Catalin Marinas
2005-01-19 15:56                 ` Jerry Van Baren
2005-01-24 17:14                   ` [U-Boot-Users] Re: Revision COntrol, Patch Database Jerry Van Baren
2005-01-24 18:33                     ` Catalin Marinas
2005-01-24 19:52                       ` Jerry Van Baren
2005-01-18 14:14         ` [U-Boot-Users] Patch for Cirrus Logic EDB9312 Cliff Brake
2005-01-19  8:33           ` llandre
2005-01-18 15:57         ` Cory Tusar
2005-01-19  8:35           ` llandre

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=41ED32F0.3020109@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.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