Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] sup-sync-back not syncing all usual sources
Date: Thu, 30 Aug 2007 15:50:47 -0400	[thread overview]
Message-ID: <1188503036-sup-4823@mona> (raw)
In-Reply-To: <1184091559-sup-1633@south>

Excerpts from William Morgan's message of Tue Jul 10 14:21:57 -0400 2007:

> > it now spits out the names of all of my usual sources and moves deleted
> > files from some, but not all of them.
> 
> This I'm still not sure about and I can't replicate. a) Does it still
> happen with recent SVN, and b) are there any distinguishing features about
> which sources it moves stuff from and which it wrongly ignores?

i just tried running sup-sync-back without specifying any sources for a
week, then ran my script to look for messages waiting to be deleted.  my
script didn't find anything, so this seems to be working fine for me now.

thanks,

-- 
jeff covey
http://jeffcovey.net/



      reply	other threads:[~2007-08-30 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14 16:13 jeff covey
2007-06-17 20:30 ` William Morgan
2007-06-18  1:00   ` jeff covey
2007-07-10 18:21     ` William Morgan
2007-08-30 19:50       ` jeff covey [this message]

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=1188503036-sup-4823@mona \
    --to=jeff.covey@pobox.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