From: Christian Himpel <chressie@googlemail.com>
To: "Ahmed Nuaman,
Freelance Designer and Developer" <ahmed@ahmednuaman.com>
Cc: git@vger.kernel.org
Subject: Re: Getting a list of last commit's files and piping them..
Date: Mon, 28 Sep 2009 16:13:12 +0200 [thread overview]
Message-ID: <20090928141312.GA4564@mrslave> (raw)
In-Reply-To: <4f302eef91c72cd4583e0aa4707ab4c0@ahmednuaman.com>
On Mon, Sep 28, 2009 at 02:02:52PM +0100, Ahmed Nuaman, Freelance Designer and Developer wrote:
> I use git for a local versioning system and was wondering if there was a
> way that I could write a bash script that would get the paths of the files
> from the latest commit and then pipe them to ftp or ssh for deployment.
For example, to scp a complete file list from branch `topic' to
`user@server', you could use `rsync' and do something like:
git checkout topic &&
git ls-tree -r --name-only |
rsync -a -e ssh --files-from=- user@server:/path/to/dest
Note, that this is completely untested. Use at your own risk.
Regards,
chressie
prev parent reply other threads:[~2009-09-28 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 13:02 Getting a list of last commit's files and piping them Ahmed Nuaman, Freelance Designer and Developer
2009-09-28 14:01 ` Johannes Schindelin
2009-09-28 14:13 ` Christian Himpel [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=20090928141312.GA4564@mrslave \
--to=chressie@googlemail.com \
--cc=ahmed@ahmednuaman.com \
--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 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 NNTP newsgroup(s).