public inbox for
 help / color / mirror / Atom feed
From: "Pierre Muller" <>
To: "'Tom Tromey'" <>,
	"'Joel Brobecker'" <>
Cc: <>
Subject: RE: [Archer] Remote repository and git push command
Date: Fri, 11 Mar 2011 10:32:00 -0000	[thread overview]
Message-ID: <000001cbdfd7$979b6f60$c6d24e20$> (raw)
In-Reply-To: <>

> -----Message d'origine-----
> De : [] De la part de
> Tom Tromey
> Envoyé : jeudi 10 mars 2011 22:51
> À : Joel Brobecker
> Cc : Pierre Muller;
> Objet : Re: [Archer] Remote repository and git push command
> Joel> I don't know what the policy is on the Archer branch, or whether
> Joel> there is one or not.
> We don't really have one.
> I don't rebase the branches I push; I do that stuff locally.
> I know others have rebased public branches, though.
> I think the important consideration is whether anybody else is likely to
> be working with you on the branch.
  As I don't expect this for now, 
I tried to push my locally rebased files:

$ git push  --force
Counting objects: 59, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (35/35), done.
Writing objects: 100% (35/35), 15.75 KiB, done.
Total 35 (delta 30), reused 0 (delta 0)
remote: error: denying non-fast-forward
refs/heads/archer-muller-windows-multi (
you should pull first)
To ssh://
 ! [remote rejected] archer-muller-windows-multi ->
error: failed to push some refs to 'ssh://'

What does that mean?


  reply	other threads:[~2011-03-11 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 10:30 Pierre Muller
2011-03-09 10:44 ` [Archer] " Joel Brobecker
2011-03-10 21:51   ` Tom Tromey
2011-03-11 10:32     ` Pierre Muller [this message]
2011-03-11 11:35       ` Jan Kratochvil

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001cbdfd7$979b6f60$c6d24e20$' \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).