From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: git@vger.kernel.org
Subject: [little BUG] pushing to existing branch with remote-helper shows [new branch]
Date: Wed, 31 Aug 2011 18:46:39 +0200 [thread overview]
Message-ID: <vpqfwkho7f4.fsf@bauges.imag.fr> (raw)
Hi,
Nothing serious, but I think this is a little bug in transport-helper. I
noticed it working on git-remote-mediawiki, and could reproduce it with
testgit:
/tmp/clone$ git push
To testgit::/tmp/repo
* [new branch] master -> master
/tmp/clone$ date >> foo.txt; git commit -am bar
[master 4438ced] bar
1 files changed, 1 insertions(+), 0 deletions(-)
/tmp/clone$ git push
To testgit::/tmp/repo
* [new branch] master -> master
(/tmp/clone is a clone of testgit::/tmp/repo)
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
reply other threads:[~2011-08-31 16:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vpqfwkho7f4.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--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