All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "Kirill A. Korinskiy" <catap@catap.ru>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] git-push: add option --repo-all
Date: Fri, 18 Sep 2009 01:52:49 -0700 (PDT)	[thread overview]
Message-ID: <m3r5u43a8h.fsf@localhost.localdomain> (raw)
In-Reply-To: <1253258222-11475-1-git-send-email-catap@catap.ru>

"Kirill A. Korinskiy" <catap@catap.ru> writes:

> Example of usage: I write some software on my laptop and some time
> pushing to my home/private server for backup. Some time ago my
> software is done and I openin it on github, but I'm don't like kill my
> private repos. Now update a two remotes repo is'n sexy, because I'm
> need using a some shell wrapper:
> 
>     git remote show | while read repo; do git push $repo; done

Signoff?

> ---
>  Documentation/git-push.txt |    4 ++-
>  builtin-push.c             |   34 +++++++++++++++++++++-----------
>  t/t5523-push-repo-all.sh   |   46 ++++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 71 insertions(+), 13 deletions(-)
>  create mode 100755 t/t5523-push-repo-all.sh

I have created 'pushall' *alias* for that purpose, but I think that
such functionality would be better added to "git remote" rather than
to "git push".

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2009-09-18  8:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18  7:17 [PATCH] git-push: add option --repo-all Kirill A. Korinskiy
2009-09-18  8:52 ` Jakub Narebski [this message]
2009-09-18 10:44   ` Kirill A. Korinskiy
     [not found]   ` <877hvwzkw7.wl%catap@catap.ru>
2009-09-18 11:02     ` Jakub Narebski
2009-09-18 11:15       ` Paolo Bonzini
2009-09-18 16:42   ` Junio C Hamano

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=m3r5u43a8h.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=catap@catap.ru \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 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.