public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Trouble with Git 2.1.x pushing to repos over Samba
Date: Thu, 30 Apr 2015 11:17:00 -0000	[thread overview]
Message-ID: <20150430111752.GN3657@calimero.vinschen.de> (raw)
In-Reply-To: <CAOC2fq8iArHbVJzBcdrCFUNf4uTwt9b-2=WN82uyryFox6vVEw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 951 bytes --]

On Apr 30 04:11, Michael Enright wrote:
> Corinna,
> 
> Do you think the snapshot would change the outcome in my case?

I think so.

> I haven't used a snapshot before. Is there a tutorial on how to get
> onto and off of a snapshot? Or should I test by using a VM?

Just download the cygwin DLL matching your architecture (x86/x86_64),
that is

  http://cygwin.com/snapshots/x86/cygwin1-20150430.dll.xz or
  http://cygwin.com/snapshots/x86_64/cygwin1-20150430.dll.xz

Unxz it, chmod +x it.  Exit all Cygwin processes (even services), move
the original cygwin1.dll to a safe place.  Copy the snapshot DLL into
its place, renaming it to cygwin1.dll.  Start a shell.  Test.  Exit the
shell.  Remove the new DLL and move the original DLL back into its
place.  That's it.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-04-30 11:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30  4:26 Michael Enright
2015-04-30  8:44 ` John Orr
2015-04-30  8:54   ` John Orr
2015-04-30 10:56   ` Corinna Vinschen
2015-04-30 11:11     ` Michael Enright
2015-04-30 11:17       ` Corinna Vinschen [this message]
2015-04-30 15:02         ` Michael Enright
2015-04-30 15:10           ` Corinna Vinschen
2015-04-30 23:54     ` John Orr

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=20150430111752.GN3657@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@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).