From: Olaf Hering <olaf@aepfle.de>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: git@vger.kernel.org
Subject: Re: how to reduce disk usage for large .git dirs?
Date: Fri, 14 Nov 2014 11:54:18 +0100 [thread overview]
Message-ID: <20141114105417.GA8954@aepfle.de> (raw)
In-Reply-To: <20141114103013.GC2549@aepfle.de>
On Fri, Nov 14, Olaf Hering wrote:
> On Fri, Nov 14, Fredrik Gustafsson wrote:
>
> > On Fri, Nov 14, 2014 at 11:14:27AM +0100, Olaf Hering wrote:
> > > So my repo-master is now "bare". I pushed from repo-branchA into
> > > repo-master and see my commits in both repos. But pushing from
> > > repo-master to the remote fails because repo-master does not have
> > > outstanding remote commits. However, git fetch doesnt do anything:
> >
> > Are you mixing up your branches? So that you're updating one branch in
> > your master repo but trying to push an other branch to your remote repo?
>
> I dont think so. I have branchA in repo-branchA, and a 'git push origin
> branchA' puts it into repo-master.
> How is a bare repo supposed to be updated? Is a simple 'git fetch --all'
> supposed to work?
Is there s a slim chance that I have to fetch in repo-master before
doing a git push in repo-branchA? git remote show origin shows that some
branches are out of date.
Olaf
next prev parent reply other threads:[~2014-11-14 10:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 11:14 how to reduce disk usage for large .git dirs? Olaf Hering
2014-11-13 11:49 ` Fredrik Gustafsson
2014-11-13 12:03 ` Olaf Hering
2014-11-14 12:32 ` Jakub Narębski
2014-11-13 12:02 ` Roger Gammans
2014-11-13 12:21 ` Olaf Hering
2014-11-13 12:09 ` Duy Nguyen
2014-11-13 15:44 ` Olaf Hering
2014-11-13 16:03 ` Fredrik Gustafsson
2014-11-13 16:08 ` Johan Herland
2014-11-13 20:15 ` Jeff King
2014-11-14 10:14 ` Olaf Hering
2014-11-14 10:24 ` Fredrik Gustafsson
2014-11-14 10:30 ` Olaf Hering
2014-11-14 10:54 ` Olaf Hering [this message]
2014-11-14 11:24 ` Olaf Hering
2014-11-14 15:06 ` Andreas Schwab
2014-11-25 14:32 ` Olaf Hering
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=20141114105417.GA8954@aepfle.de \
--to=olaf@aepfle.de \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.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).