public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: The Vulgar And Quite Professionally Mean Cygwin-Talk Maiming
	List <cygwin-talk@cygwin.com>
Subject: Re: MVFS results
Date: Fri, 17 Jul 2009 00:28:00 -0000	[thread overview]
Message-ID: <4A5FC746.4080309@gmail.com> (raw)
In-Reply-To: <20090717000248.GB20981@ednor.casa.cgf.cx>

Christopher Faylor wrote:
> On Thu, Jul 16, 2009 at 11:13:43PM +0000, Eric Blake wrote:
>> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
>>> Oh well.  Ok, I planned to check this change in and let you then test
>> >from CVS.  But since that's a problem for you, here's the patch.  The
>>> important part is that Cygwin should now always create symlinks as
>>> shortcuts on MVFS, regardless of the CYGWIN=winsymlink setting.  Please
>>> check.
>> Not quite.  I've finally got my tree in the state where I could apply
>> this patch.  For the record (more documenting it for myself, than
>> anything else), I used setup.exe to get 1.7.0-51 sources, used 'git
>> init && git add .  && git commit -m 1.7.0-51' to make it easier to
>> track commits, then ran these commands to grab all CVS changes since
>> that point:
>>
>> $ wget
>> http://cygwin.com/ml/cygwin-cvs/2009-q3/msg0003{0,1,2,3,4,5,6,7,8}.html
>>
>> $ for f in msg*.html; do sed -n
>> 's,.*\(http://sources.redhat.com/cgi-bin[^<]*\)<.*,\1, s,&amp;,\&,gp'
>> $f > ${f%.html}.txt; done
>>
>> $ for f in msg0003*; do while read file; do wget -O patch.txt "$file";
>> patch -p2 < patch.txt; done < $f ; git commit -a -m "fold in $f"; done
> 
> I always just use the toggle switches on the front panel of my computer.
> 
> Much easier.
> 
> cgf

  I always just bang two rocks together.  With a cute fluffy kitten trapped in
between.  It doesn't have quite as much computational power, but at least it's
needlessly sadistic and cruel.

  Much more satisfying.

    cheers,
      DaveK

  parent reply	other threads:[~2009-07-17  0:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <loom.20090715T192219-408@post.gmane.org>
     [not found] ` <20090715204831.GA27613@calimero.vinschen.de>
     [not found]   ` <loom.20090715T213245-387@post.gmane.org>
     [not found]     ` <20090716090703.GH27613@calimero.vinschen.de>
     [not found]       ` <h3mrap$f0n$1@ger.gmane.org>
     [not found]         ` <20090716094505.GJ27613@calimero.vinschen.de>
     [not found]           ` <4A5EFC69.10408@gmail.com>
2009-07-16 11:15             ` Dave Korn
2009-07-17  0:32               ` Christopher Faylor
2009-07-17  0:43                 ` Dave Korn
2009-07-17  0:52                   ` Dave Korn
     [not found]       ` <loom.20090716T133741-21@post.gmane.org>
     [not found]         ` <20090716151121.GO27613@calimero.vinschen.de>
     [not found]           ` <loom.20090716T154525-611@post.gmane.org>
     [not found]             ` <20090716165112.GS27613@calimero.vinschen.de>
     [not found]               ` <loom.20090716T165527-559@post.gmane.org>
     [not found]                 ` <20090716174525.GT27613@calimero.vinschen.de>
     [not found]                   ` <loom.20090716T225222-72@post.gmane.org>
     [not found]                     ` <20090717000248.GB20981@ednor.casa.cgf.cx>
2009-07-17  0:18                       ` Eric Blake
2009-07-17  0:30                         ` Dave Korn
2009-07-17  0:28                       ` Dave Korn [this message]
2009-07-17  8:00                         ` Corinna Vinschen
2009-07-17 14:14                           ` Dave Korn
2009-07-17 18:29                             ` Christopher Faylor
     [not found]                       ` <COL102-W45E99859A86FACF4F28D53B51E0@phx.gbl>
     [not found]                         ` <4A5FCD8E.8090805@gmail.com>
     [not found]                           ` <alpine.LRH.0.9999.0907170932050.23720@honker.vgersoft.com>
2009-07-17 14:18                             ` 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=4A5FC746.4080309@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=cygwin-talk@cygwin.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).