From: Andreas Ericsson <ae@op5.se>
To: Matt Graham <mdg149@gmail.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Daniel Quinlan <danq@brtt.com>,
git@vger.kernel.org
Subject: Re: help with git usage
Date: Wed, 30 Apr 2008 15:09:43 +0200 [thread overview]
Message-ID: <48186F97.6080509@op5.se> (raw)
In-Reply-To: <1c5969370804300502obbc5a63v4c2c1a1175084237@mail.gmail.com>
Matt Graham wrote:
> On Tue, Apr 29, 2008 at 2:07 PM, Daniel Barkalow <barkalow@iabervon.org> wrote:
>> On Tue, 29 Apr 2008, Daniel Quinlan wrote:
>>
>> > I've been trying to use git for awhile now, (and I've read a lot of
>> > documentation, though maybe my
>> > comprehension has not been high enough) but there are several operations which
>> > I
>> > can't figure out:
>> >
>> > 1) After cloning a repository from work at home, making some changes and
>> > committing them,
>> > I use "git push" to push them back to the work repository. The changes seem
>> > to make it to the
>> > work repository (I see the commit message in git log), but I can't figure out
>> > how to get the
>> > changes into the working set at work. (evidently not merge, checkout or reset
>> > -- seems like it
>> > should be merge, but)
>>
>> You shouldn't push to a non-bare repository.
>
> Is there any reason it wouldn't be appropriate to make git refuse to
> push to non-bare repositories?
It has several very valid uses. Newcomers who don't know what happens are
often better off not doing it, which is why it's not recommended. Making
git refuse would prevent the valid uses altogether though.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-04-30 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 17:37 help with git usage Daniel Quinlan
2008-04-29 18:07 ` Daniel Barkalow
2008-04-30 7:39 ` Jakub Narebski
2008-05-07 22:41 ` Daniel Quinlan
2008-05-08 0:16 ` Julian Phillips
2008-05-08 20:01 ` Dirk Süsserott
2008-05-08 23:07 ` Jakub Narebski
2008-04-30 12:02 ` Matt Graham
2008-04-30 13:09 ` Andreas Ericsson [this message]
2008-04-30 8:22 ` Richard Quirk
2008-04-30 10:39 ` Jakub Narebski
2008-04-30 11:50 ` Richard Quirk
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=48186F97.6080509@op5.se \
--to=ae@op5.se \
--cc=barkalow@iabervon.org \
--cc=danq@brtt.com \
--cc=git@vger.kernel.org \
--cc=mdg149@gmail.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 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 NNTP newsgroup(s).