All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Burton <markb@ordern.com>
To: git@vger.kernel.org
Subject: Bugs in git-gui and git-push when pushing src:dst to mirror?
Date: Tue, 2 Dec 2008 13:08:59 +0000	[thread overview]
Message-ID: <20081202130859.43ba54f6@crow> (raw)


Hi,

Using git 1.6.0.4.

I just tried to push using git-gui to a mirror of the current
repository and it failed because git-gui included a src:dest refspec
and that upset git-push as the remote is a mirror. So, I think that it would
be useful if git-gui notices when the remote is a mirror and does not
pass the refspec (I shall try to form a patch later when I have some time).

The other issue is that although git-push did print the usage blurb,
it didn't actually produce a message saying what it's problem was.
Looking at the source, I would have expected to have seen "--mirror
can't be combined with refspecs" printed but it didn't happen. Here's
what I got when I run the same command (as attempted by git-gui) on the
command line:

$ git push -v tako refs/heads/multi-stream:refs/heads/multi-stream
usage: git push [--all | --mirror] [--dry-run] [--tags] [--receive-pack=<git-receive-pack>] [--repo=<repository>] [-f | --force] [-v] [<repository> <refspec>...]

    -v, --verbose         be verbose
    --repo <repository>   repository
    --all                 push all refs
    --mirror              mirror all refs
    --tags                push tags
    --dry-run             dry run
    -f, --force           force updates
    --thin                use thin pack
    --receive-pack <receive-pack>
                          receive pack program
    --exec <receive-pack>
                          receive pack program


Any ideas?

Cheers,

Mark

             reply	other threads:[~2008-12-02 13:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 13:08 Mark Burton [this message]
2008-12-02 17:49 ` Bugs in git-gui and git-push when pushing src:dst to mirror? Mark Burton

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=20081202130859.43ba54f6@crow \
    --to=markb@ordern.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 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.