From: Ben Lau <benlau@ust.hk>
To: Andreas Ericsson <ae@op5.se>
Cc: git@vger.kernel.org
Subject: Re: Clone a repository with only the objects needed for a single tag
Date: Wed, 02 Nov 2005 17:10:57 +0800 [thread overview]
Message-ID: <436882A1.1020207@ust.hk> (raw)
In-Reply-To: <43687DAE.2010604@op5.se>
Andreas Ericsson wrote:
> Ben Lau wrote:
>
>> Hi Junio,
>>
>> It works! Thanks a lot.
>>
>> However, it has a problem when involves the gitk/git-log.
>
>
>
> Both those programs use the history, which you don't have. With a
> shallow repository like this some commands just won't work. git-*log
> and gitk are among those.
yes, it is expected. However, I just think with a fake parent like what
.git/info/grafts could provide may solve the issue. At least it make
git-log be happy to show the only log message in the shallow repository
without any error.
The rest of problem is gitk could not show any item like what git-log shown.
I am not sure is it right to have a pair of same ID into
.git/info/grafts or it should be solved by a little patch to gitk.
>
>>
>> git-log/gitk do not complains afterward, but it also make gitk shows
>> nothing during run. Any solution?
>>
>
> * Get a second machine with more disk-space and run the history tools
> there. If you use it as mothership and push your commits to it you'll
> be able to track your changes from the laptop as well.
>
> * Get a larger disk. They're not terribly expensive now adays.
>
> * Check out one tag (i.e. release) more than you need. Then you'll get
> history back to that tag.
>
next prev parent reply other threads:[~2005-11-02 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 2:02 Clone a repository with only the objects needed for a single tag Ben Lau
2005-11-02 7:01 ` Junio C Hamano
2005-11-02 8:27 ` Ben Lau
2005-11-02 8:49 ` Andreas Ericsson
2005-11-02 9:10 ` Ben Lau [this message]
2005-11-02 9:20 ` 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=436882A1.1020207@ust.hk \
--to=benlau@ust.hk \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
/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).