From: Linus Torvalds <torvalds@linux-foundation.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: basics... when reading docs doesn't help
Date: Thu, 29 Mar 2007 15:35:29 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0703291531030.6730@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0703292354100.10351@poirot.grange>
On Fri, 30 Mar 2007, Guennadi Liakhovetski wrote:
> > >
> > > How about suggesting "clone -l -s"?
>
> Yes, but how do "advanced git users" kernel developers work? Do they just
> do 1 clone and build / clean every time they want to test another
> configuration / arch, or do they clone -l or what? Do they create branches
> for each development thread, then pull / push between trees?...
I suspect it depends on the developer.
I end up just using different branches and switching between them, but
then, my branches tend to all be pretty small test-stuff (I only end up
using one main branch, since 99% of what I do is merge other peoples stuff
that has already gone through a test-cycle).
> But I don't want to re-build. Apart from i386 I build for a couple of ARM
> and PPC targets too...
You're probably fine with "git clone -l -s" then.
> Strange. Is my git 1.4.0 criminally broken? I have a clone of Linus' tree
> on a USB disk on ext3 without any objects, which I just cloned at some
> point and then did a couple of pulls from the same source. Now
>
> 1545084 /mnt/sda2/kernel-git/linux-2.6/
> 1255084 /mnt/sda2/kernel-git/linux-2.6/.git
The old git that always exploded all pulls and generated lots of loose
objects? You can check with "git count-objects".
And to fix it, just do a "git gc" (or with older git versions, the secret
handshake is just a simple "git repack -a -d").
> But that's a freshly cloned tree, without any pulls. I re-cloned it,
> because the tree I had earlier had the problem with each pull:
>
> Unpacking 12452 objects
> 100% (12452/12452) done
> * refs/heads/origin: does not fast forward to branch 'master' of
> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc;
> not updating.
Sounds like either Paul re-based his tree, or you did some work on your
"origin" branch..
Linus
next prev parent reply other threads:[~2007-03-29 22:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 20:50 basics... when reading docs doesn't help Guennadi Liakhovetski
2007-03-29 21:16 ` J. Bruce Fields
2007-03-29 21:26 ` Junio C Hamano
2007-03-29 21:46 ` J. Bruce Fields
2007-03-29 22:13 ` Guennadi Liakhovetski
2007-03-29 22:35 ` Linus Torvalds [this message]
2007-03-30 18:16 ` Guennadi Liakhovetski
2007-03-30 18:48 ` Linus Torvalds
2007-03-30 19:49 ` Guennadi Liakhovetski
2007-03-30 20:06 ` Linus Torvalds
2007-03-30 20:23 ` Theodore Tso
2007-03-30 20:39 ` Junio C Hamano
2007-03-30 21:11 ` Guennadi Liakhovetski
2007-03-30 2:43 ` Theodore Tso
2007-03-30 14:49 ` J. Bruce Fields
2007-03-30 18:02 ` Andreas Herrmann
2007-03-30 18:24 ` Guennadi Liakhovetski
2007-03-29 22:27 ` Matthieu Moy
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0703291531030.6730@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=g.liakhovetski@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).