public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jason Tishler <jason@tishler.net>
To: cygwin@cygwin.com
Subject: Re: rebaseall 2.4-1 : problems?
Date: Sun, 17 Jul 2005 12:33:00 -0000	[thread overview]
Message-ID: <20050717123120.GE3540@tishler.net> (raw)
In-Reply-To: <Pine.OSF.4.21.0507170157230.32229-100000@ax0rm1.roma1.infn.it>

Angelo,

On Sun, Jul 17, 2005 at 02:08:41AM +0200, Angelo Graziosi wrote:
> I send you a simple report.
> 
> I have tried to use the new version of "rebaseall".
> 
> Steps followed:
> 
> 1) Add "C:\cygwin\bin" and "C:\cygwin\usr\X11R6\bin" to Windows path

What happens if you prepend the above to the Windows PATH?

> [snip]
> 
> $ rebaseall -v
> grep: Could not open '/proc/1056/exename'
> grep: Could not open '/proc/1324/exename'
> Error: Invalid option -E

Are you sure your PATH is hitting the Cygwin grep (and egrep)?

> (without adding the 'bin' to Windows path, one gets only "not found") 

The above should be expected.

> [snip]
> ash 20040127-3 (rebase-2.4-1-README says ash 20040127-1 but with this
>                 version of ash it does not work at all, ash.exe does not
>                 exist)

The above is a bug in the README.  I have fixed it for the next release.

Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2005-07-17 12:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-17  0:08 Angelo Graziosi
2005-07-17 12:33 ` Jason Tishler [this message]
2005-07-17 21:49 Angelo Graziosi
2005-07-18 11:46 ` Jason Tishler

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=20050717123120.GE3540@tishler.net \
    --to=jason@tishler.net \
    --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).