public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: [RFU] lftp
Date: Tue, 28 May 2013 09:28:00 -0000	[thread overview]
Message-ID: <det8q8hnnpujc35rrke6pcm3g3fguc5frr@4ax.com> (raw)
In-Reply-To: <51A4490A.2010500@users.sourceforge.net>

> On 2013-05-27 15:46, Andrew Schulman wrote:
> > wget \
> >   http://home.comcast.net/~andrex2/cygwin/lftp/lftp-4.4.7-1.tar.bz2 \
> >   http://home.comcast.net/~andrex2/cygwin/lftp/lftp-4.4.7-1-src.tar.bz2 \
> >   http://home.comcast.net/~andrex2/cygwin/lftp/lftp-debuginfo-4.4.7-1.tar.bz2
> 
> Uploaded, and removed 4.4.0-1.
> 
> But in the future, please use the cygport-generated structure for your 
> uploads and add the necessary flags to wget (e.g. -r -nH --cut-dirs=2), 
> so that lftp-debuginfo is a subdirectory of lftp as it should be.  That 
> will make it much easier to upload in the future.

I'm happy to oblige, and I see that lftp-debuginfo is in its own directory in
the mirrors.  But what you see above is how cygport is creating the files - all
together in the same directory as my .cygport file.  So this is the first I've
heard of it.

If cygport is supposed to be putting lftp-debuginfo into its own directory, I'm
not sure why it isn't.  Configuration setting?  Or maybe it wants the directory
already to exist?  I'll see what I can figure out when I get back to that
machine.

  reply	other threads:[~2013-05-28  9:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27 20:44 Andrew Schulman
2013-05-27 20:46 ` Andrew Schulman
2013-05-28  6:05   ` Yaakov (Cygwin/X)
2013-05-28  9:28     ` Andrew Schulman [this message]
2013-05-28 10:21       ` Corinna Vinschen
2013-05-28 12:56         ` marco atzeri
2013-05-28 18:06         ` Andrew Schulman
2013-05-28 19:01           ` Corinna Vinschen
  -- strict thread matches above, loose matches on Subject: below --
2013-08-10 18:27 Schulman, Andrew
2013-08-10 21:12 ` Ken Brown
2013-03-03 15:40 Andrew Schulman
2013-03-03 17:26 ` Christopher Faylor
2013-03-03 23:40 ` Chris Sutcliffe
2013-03-04  3:58   ` Yaakov
2013-03-04 18:38   ` Christopher Faylor
2013-03-04 21:23     ` Andrew Schulman
2013-03-04 21:28       ` Christopher Faylor
2012-10-04  1:34 Andrew Schulman
2012-10-05  1:38 ` Christopher Faylor
2012-05-31 18:53 Andrew Schulman
2012-05-31 19:29 ` Andrew Schulman
2012-06-01 10:18   ` Corinna Vinschen
2012-04-17 18:12 Andrew Schulman
2012-04-17 18:49 ` Yaakov (Cygwin/X)
2012-04-17 21:02   ` Andrew Schulman
2011-05-03 14:21 Andrew Schulman
2011-05-03 14:25 ` Corinna Vinschen
2011-04-26 14:02 Andrew Schulman
2011-04-26 15:48 ` Corinna Vinschen
2010-10-21 19:50 Andrew Schulman
2010-10-21 23:10 ` Yaakov (Cygwin/X)
2010-10-22 13:53   ` Andrew Schulman
2010-10-22 17:14     ` Yaakov (Cygwin/X)
2010-10-22 14:07   ` Andrew Schulman
2010-10-22 14:40     ` Christopher Faylor
2010-01-07 15:18 Andrew Schulman
2010-01-07 17:11 ` Andrew Schulman
2010-01-07 17:43   ` Corinna Vinschen
2010-01-07 17:53     ` Andrew Schulman
2010-01-07 18:08       ` Corinna Vinschen
2009-01-21 20:29 Andrew Schulman
2009-01-22  9:00 ` Corinna Vinschen

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=det8q8hnnpujc35rrke6pcm3g3fguc5frr@4ax.com \
    --to=schulman.andrew@epamail.epa.gov \
    --cc=cygwin-apps@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).