From: Simon 'corecode' Schubert <corecode@fs•ei.tum.de>
To: Junio C Hamano <junkio@cox•net>
Cc: Steven Grimm <koreth@midwinter•com>, git@vger•kernel.org
Subject: Re: Pushing to a non-bare repository
Date: Sat, 03 Feb 2007 10:46:05 +0100 [thread overview]
Message-ID: <45C459DD.8080201@fs.ei.tum.de> (raw)
In-Reply-To: <7vfy9ndiqp.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
Junio C Hamano wrote:
>> This keeps coming up as I introduce people to git. In previous
>> discussions, the conclusion often seems to be that users don't really
>> know what they want the semantics to be.
>
> I do not think that was the conclusion. My suggestion to you
> would be to stop thinking as if push is a converse of pull
> (because it is not; push is a counterpart of fetch), and leave
> push as is.
However, your suggestion does not help people who don't know better. Pushing into the HEAD branch of another repo breaks stuff there. Badly. This should be prevented, really.
I don't say "Push needs to behave like a fast forward pull", because that's wrong. You can't just change the workdir, possibly due to permissions problems. But push has to abort if you try to forward HEAD on the remote, except if it is bare, of course.
cheers
simon
--
Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\
Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-02-03 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 3:01 Pushing to a non-bare repository Steven Grimm
2007-02-03 3:26 ` Junio C Hamano
2007-02-03 9:46 ` Simon 'corecode' Schubert [this message]
2007-02-03 19:42 ` Junio C Hamano
2007-02-03 19:48 ` Linus Torvalds
2007-02-03 21:18 ` 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=45C459DD.8080201@fs.ei.tum.de \
--to=corecode@fs$(echo .)ei.tum.de \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
--cc=koreth@midwinter$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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