From: Mathias Lafeldt <misfire@debugon.org>
To: Maaartin <grajcar1@seznam.cz>
Cc: git@vger.kernel.org
Subject: Re: Pushing everything
Date: Sun, 31 Oct 2010 12:32:45 +0100 [thread overview]
Message-ID: <4CCD53DD.4090605@debugon.org> (raw)
In-Reply-To: <loom.20101031T113039-859@post.gmane.org>
On 10/31/2010 11:48 AM, Maaartin wrote:
> Andreas Schwab <schwab <at> linux-m68k.org> writes:
>>
>> Tay Ray Chuan <rctay89 <at> gmail.com> writes:
>>
>>> On Sun, Oct 31, 2010 at 1:47 PM, Maaartin <grajcar1 <at> seznam.cz> wrote:
>>>> I'd like to push all my branches and tags to the server, but for whatever
> reason
>>>> "--all" ignores tags and is incompatible with "--tags". I could imagine
> there's
>>>> a reason I'm not experienced enough to see?
>>>
>>> You can spell the refs explicitly, like this:
>>>
>>> $ git push refs/heads/* refs/tags/*
>>
>> The first argument needs to be a reference to a repository, so insert an
>> origin here.
>
> Nice, that works. It answers only a part of my questions, but maybe I can
> complete it. I want to use a repo as both a private backup (which everybody may
> read but nobody should) and a shared base. So maybe something like
>
> git push origin +refs/heads/*:refs/heads/maaartin-* +refs/tags/*:refs/tags/
> maaartin-* :
>
> would do both the backup (where everything gets prefixed by my name) and normal
> pushing of tracking branches. Could it work? Should I try it out or can it be
> destructive?
Hi,
why don't you try pushing to a local clone first, and then check the results?
This puts your data at no risk.
-Mathias
next prev parent reply other threads:[~2010-10-31 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 5:47 Pushing everything Maaartin
2010-10-31 6:43 ` Tay Ray Chuan
2010-10-31 9:48 ` Andreas Schwab
2010-10-31 10:48 ` Maaartin
2010-10-31 11:32 ` Mathias Lafeldt [this message]
2010-10-31 12:30 ` Konstantin Khomoutov
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=4CCD53DD.4090605@debugon.org \
--to=misfire@debugon.org \
--cc=git@vger.kernel.org \
--cc=grajcar1@seznam.cz \
/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.