git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Benton <b3nton@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Configuring git to for forget removed files
Date: Sun, 21 Feb 2010 13:32:34 +0000	[thread overview]
Message-ID: <4B8135F2.3000709@gmail.com> (raw)
In-Reply-To: <20100221024746.GA9628@progeny.tock>

On 21/02/10 02:47, Jonathan Nieder wrote:
> Maybe you could keep the build scripts in a git repository and
> synchronizing the tarballs out of line with some other tool, such as
> rsync or unison.

Thanks, that seems to do what I want. I'll use git to keep track of the bash scripts and
rsync -r --delete --ignore-existing --progress --exclude '.git'
to synchronise the source tarballs

Andy

  reply	other threads:[~2010-02-21 13:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-20 10:37 Configuring git to for forget removed files Andrew Benton
2010-02-20 15:41 ` Tim Visher
2010-02-20 18:50 ` Avery Pennarun
2010-02-20 19:16 ` Junio C Hamano
2010-02-21  2:47 ` Jonathan Nieder
2010-02-21 13:32   ` Andrew Benton [this message]
2010-02-21 20:32 ` Larry D'Anna
2010-02-21 21:14   ` Jacob Helwig

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=4B8135F2.3000709@gmail.com \
    --to=b3nton@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.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 NNTP newsgroup(s).