git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "eric miao" <eric.y.miao@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Will git have a baseline feature or something alike?
Date: Sat, 1 Mar 2008 16:41:49 +0100	[thread overview]
Message-ID: <200803011641.49874.jnareb@gmail.com> (raw)
In-Reply-To: <f17812d70803010610o39cdf327x995c9e2e75a9edba@mail.gmail.com>

On Sat, 1 Mar 2008, eric miao wrote:
> On Fri, Feb 29, 2008 at 9:21 PM, Jakub Narebski <jnareb@gmail.com> wrote:

[could you please remove irrelevant parts of the reply? TIA]

>> There is so called "shallow clone" feature, which allows to clone only
>> part of history. Currently it dupports only --depth, i.e. number of
>> commits from tips; it could I guess support providing tag as
>> delimiter. (You are welcome to implement it ;-).
>>
> 
> I haven't ever used the shallow clone, but it looks still a bit different
> from what I thought originally, say, if I download linux-2.6.24.tar.bz2
> from kernel.org, that's about 40MB and should be a fair amount.
> I then unpack and "git init", I expect it to recognize it's a v2.6.24,
> and I can thereafter use "git fetch" to fetch those commits after
> v2.6.24 from git.kernel.org. Is this possible?

No, this doesn't work and couldn't work. The tarfile contains only
_contents_ of the working directory, and perhaps commit-id, but it
doesn't contain even shred of history. Git has no information of
where this content is in linux kernel git history.

You have to do "git clone --depth=1 <url>"; surrently there is no
way to specify "git clone --from=<tag> <url>". I guess you can try
to get info browsing gitweb, and fudge with grafts.

-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2008-03-01 15:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29  9:23 Will git have a baseline feature or something alike? eric miao
2008-02-29  9:56 ` Sean
2008-02-29 10:38   ` Karl Hasselström
2008-02-29 13:21 ` Jakub Narebski
2008-03-01  7:04   ` Sam Vilain
2008-03-01 12:39     ` Jakub Narebski
2008-03-01 13:20       ` Sam Vilain
2008-03-02 19:38         ` Jan Hudec
2008-03-02 21:29         ` Martin Langhoff
2008-03-01 14:10   ` eric miao
2008-03-01 14:29     ` Nguyen Thai Ngoc Duy
2008-03-01 15:41     ` Jakub Narebski [this message]
2008-03-01 17:30       ` Eyvind Bernhardsen
2008-03-01 18:00         ` Jakub Narebski
2008-03-02 14:04           ` Shawn O. Pearce
2008-03-01 20:43         ` David Brown

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=200803011641.49874.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=eric.y.miao@gmail.com \
    --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).