From: vasudeva@linkswarm.com (vasudeva)
Subject: [sup-talk] sup-sync-back reports: Nothing to do
Date: Mon, 25 Feb 2008 12:53:02 -0500 [thread overview]
Message-ID: <1203961949-sup-3973@lenin> (raw)
In-Reply-To: <1203959676-sup-1952@south>
Excerpts from William Morgan's message of Mon Feb 25 12:17:28 -0500 2008:
> Reformatted excerpts from vasudeva's message of 2008-02-21:
> > Nothing to do.
>
> I've improved this message in git. You need to specify least one of
> --drop-deleted, --move-deleted, --drop-spam, or --move-spam.
Thanks -- that was it.
--
linkswarm.com :: Collaborative Insolence
vasudeva.linkswarm.com/gallery :: For The Faint of Heart
prev parent reply other threads:[~2008-02-25 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 0:17 vasudeva
2008-02-25 17:17 ` William Morgan
2008-02-25 17:53 ` vasudeva [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=1203961949-sup-3973@lenin \
--to=vasudeva@linkswarm.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