All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Weber <marco-oweber@gmx.de>
To: Git Mailing List <git@vger.kernel.org>
Subject: FTP Synchronization
Date: Thu, 11 Jun 2009 02:03:42 +0200	[thread overview]
Message-ID: <20090611000342.GA20699@gmx.de> (raw)

Has anyone a FTP synchranization which behaves like this yet?

1) get current version from ftp by readitg $REMOTE/hash
2) calculate git-diff `ftp get $REMOTE/hash`..HEAD
3) ftp push all files which have changed and
   ftp rm all files which have been deleted
4) write HEAD to $REMOTE/hash

What happens if there is a failure in the middle?
Then 4) doesn't take place and all the actions will be replayed
(probably ignoring errors). Also there should be a sync option recopying
all files which are know to git at HEAD.

I don't want to use bash because I can't keep a FTP connection open, can
I? (Maybe using lfpt and stdin redirection hacks ?)
git perl lib support is better than python support, right?

If not how to do this? Maybe I should look at the git diff code to get
to know or start comparing the git ls-tree output or such?

Of course I'd like this to be as fast as possible.

Marc Weber

                 reply	other threads:[~2009-06-11  0:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090611000342.GA20699@gmx.de \
    --to=marco-oweber@gmx.de \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.