public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: geneSmith <gene.smith@sea.siemens.com>
To: insight@sources.redhat.com
Subject: Re: Can't find source files
Date: Tue, 12 Oct 2004 16:26:00 -0000	[thread overview]
Message-ID: <ckh0jv$si7$1@sea.gmane.org> (raw)
In-Reply-To: <NUTMEGkUlvFczukpHnh000003f2@NUTMEG.CAM.ARTIMI.COM>

Dave Korn wrote, On 10/12/2004 11:59 AM:

>>-----Original Message-----
>>From: Dickinson, Derek 
>>Sent: 12 October 2004 16:39
>>To: 'Dave Korn'; 'geneSmith'; insight
>>Subject: RE: Can't find source files
>>
>>Hopefully this isn't too off subject ...
>>
>>We use a symbolic link to solve the problem that Gene is experiencing
> 
> 
> 
>   Absolutely, it's exactly the sort of problem that they were designed to
> solve.  
> 
>   Since we're discussing cygwin, I'll just mention that cygwin mountpoints
> are another handy way of translating paths between different systems.
> 
>   I was gonna suggest either/and/or/both of these in my first response to
> Gene, but then I thought it might be more interesting to solve the problem
> rather than just work round it without knowing what/how/why.
> 
> 
>     cheers, 
>       DaveK

I tried faking it out with symlinks but couldn't get it to work either. 
Not sure what the problem was, it was late. :)
-gene

-- 
Lit up like Levy's

  reply	other threads:[~2004-10-12 16:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12 15:39 Dickinson, Derek
2004-10-12 16:00 ` Dave Korn
2004-10-12 16:26   ` geneSmith [this message]
2004-10-12 18:57 ` geneSmith
  -- strict thread matches above, loose matches on Subject: below --
2004-10-11 23:00 geneSmith
2004-10-12  9:05 ` Dave Korn
2004-10-12 13:31   ` geneSmith
2004-10-12 14:10     ` Dave Korn
2004-10-12 14:29       ` geneSmith
2004-10-12 15:09         ` Dave Korn
2004-10-12 16:20           ` geneSmith
2004-10-12 16:44             ` Dave Korn
2004-10-13 19:09               ` geneSmith
2004-10-14  9:41                 ` Dave Korn

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='ckh0jv$si7$1@sea.gmane.org' \
    --to=gene.smith@sea.siemens.com \
    --cc=insight@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).