public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Alfredo Knecht <aknecht@cimsi.cim.ch>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: eCos PCI problem and NEC vrc4373 build option.
Date: Wed, 30 Aug 2000 18:22:00 -0000	[thread overview]
Message-ID: <39ADB36E.6304D01C@redhat.com> (raw)
In-Reply-To: <3.0.5.32.20000831031031.00acede0@mailhost>

Alfredo Knecht wrote:
> pardon me if I somehow felt
> sympathetic with Struggling Ling Su when he got an answer which I perceived
> as "gotcha - send me the money first!".

I feel sympathetic too. Poor Ling has been suffering with problems for
quite some time, and I've already spent more time helping than by rights I
should!

> BTW, out of curiosity, how is the mechanism
> 
> >almost exactly the same as the public ones. The only differences are for
> >confidential information, ports for specific customers and unfinished code.
> 
> implemented? with CVS?

That's most of it. The mechanism is no great surprise, so it's not much of
a secret really. We have an internal CVS repository where anything
confidential is marked. A script filters out that stuff, creates a new
source tree, and then diffs that against the existing public repository. A
mug (me) then goes through and manually reads the diffs to check there were
no errors in the process (although some automatic keyword checking is also
done). If there aren't any, it then gets committed as-is. That's why I'm
happy to say that the sources are basically the same :-).

Yes this can be quite time-consuming :-). But it does mean our customers
can rest secure that confidentiality is assured! And it also means that we
know that the sources we are looking at, and the sources the net folks are
looking at are the same.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

  reply	other threads:[~2000-08-30 18:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-29 11:37 [ECOS] eCos tools binary installation under Cygwin Grant Edwards
2000-08-29 11:57 ` Jonathan Larmour
2000-08-29 12:28   ` Ling Su
2000-08-29 12:43     ` Jonathan Larmour
     [not found]       ` <39AC12F4.9C2F7678@redhat.co.uk>
2000-08-29 17:18         ` [ECOS] eCos PCI problem and NEC vrc4373 build option Ling Su
2000-08-30 15:25           ` [ECOS] " Jonathan Larmour
2000-08-30 15:51             ` Ling Su
2000-08-30 15:58               ` Jonathan Larmour
2000-08-30 16:38                 ` Alfredo Knecht
2000-08-30 17:20                   ` Jonathan Larmour
2000-08-30 18:10                     ` Alfredo Knecht
2000-08-30 18:22                       ` Jonathan Larmour [this message]
2000-08-30 17:42                   ` Ling Su
2000-08-30 18:02                     ` Jonathan Larmour
2000-08-30 18:28                       ` Ling Su
2000-08-30 18:57                         ` Jonathan Larmour
2000-08-31  3:34                           ` Nick Garnett
2000-08-31 10:57                           ` Ling Su

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=39ADB36E.6304D01C@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=aknecht@cimsi.cim.ch \
    --cc=ecos-discuss@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).