From: Dan Farina <drfarina@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: backup or mirror a repository
Date: Thu, 27 Sep 2007 19:37:43 -0700 [thread overview]
Message-ID: <1190947063.2263.46.camel@Tenacity> (raw)
In-Reply-To: <Pine.LNX.4.64.0709280253150.28395@racer.site>
On Fri, 2007-09-28 at 02:56 +0100, Johannes Schindelin wrote:
> Hi,
>
> On Thu, 27 Sep 2007, Dan Farina wrote:
> git remote rm is about removing the remote nick, not a remote branch.
Ah, I thought for some reason there'd be a "remove" (since the other
operations have long names) and, much like "ls-remote" there'd be some
"rm-remote." An insane presupposition of mine from having too little
information.
> What you should have done is "git fetch backup".
>
> Or use "origin" instead of "backup" right from the start, and then use
> "git fetch".
>
> But no pull.
I did use "pull backup" (my error for being sloppy and omitting it from
my mail) and it does work provided I do the dirty thing of doing a
subsequent reset --hard (I thought perhaps things were not yet
fully-there). Fetch does it perfectly, as you say, thanks!
> You want to remove branches from the local repo which are no longer there
> on the remote side?
>
> Then "git remote prune" is for you. For details, please see the man page.
>
I did look at prune and update, but my problem is the opposite: I want
something that will remove branches from the remote repo when they no
longer exist locally. As-is over time I will proliferate little local
branches unless I occasionally sit down and delete branches by operating
directly on the bare backup repository. (and then use prune on the
remote nodes)
Thanks,
fdr
next prev parent reply other threads:[~2007-09-28 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 19:35 backup or mirror a repository Dan Farina
2007-09-27 21:56 ` Johannes Schindelin
2007-09-28 0:51 ` Dan Farina
2007-09-28 1:56 ` Johannes Schindelin
2007-09-28 2:37 ` Dan Farina [this message]
2007-09-28 6:27 ` Junio C Hamano
2007-09-28 7:20 ` Dan Farina
2007-10-18 5:32 ` Dmitry Potapov
2007-10-30 0:33 ` Johannes Schindelin
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=1190947063.2263.46.camel@Tenacity \
--to=drfarina@gmail.com \
--cc=Johannes.Schindelin@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 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).