All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Basin <basinilya@gmail.com>
To: git@vger.kernel.org
Cc: "Eric S. Raymond" <esr@thyrsus.com>
Subject: Does git fast-import support deltas?
Date: Fri, 19 Apr 2013 09:29:31 +0400	[thread overview]
Message-ID: <1095757971.20130419092931@gmail.com> (raw)
In-Reply-To: <20130418094326.GB11038@thyrsus.com>

Hi list.
Here's what I mean:
1) a created a git repo from a foreign source using git fast-import
2) new commits were added to the foreign source

Can I create a fast-import input stream not containing the commits
already existing in my git repo and import it?

I tried to create such streams with:
    cvsps --fast-export -d ...
and from a shallow git repo, but the new commits are not imported
(unless the import stream contains a new branch)

  reply	other threads:[~2013-04-19  5:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14  8:18 cvsps: bad usage: invalid argument --norc Ilya Basin
2013-04-14  8:48 ` Ilya Basin
2013-04-14  9:47   ` John Keeping
2013-04-14 11:33   ` State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc) Eric S. Raymond
2013-04-15  5:00     ` Michael Haggerty
2013-04-15 17:58     ` Ilya Basin
2013-04-15 20:43       ` Jakub Narębski
2013-04-18  9:43       ` Eric S. Raymond
2013-04-19  5:29         ` Ilya Basin [this message]
2013-04-19  5:44           ` Does git fast-import support deltas? Felipe Contreras
2013-04-19  6:13           ` Jonathan Nieder
2013-04-20 10:22         ` Re[2]: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc) Ilya Basin
2013-04-23 17:50           ` Eric S. Raymond
2013-04-23 18:30             ` Re[2]: " Ilya Basin
2013-04-23 21:06               ` Eric S. Raymond
2013-04-24  4:47                 ` Re[2]: " Ilya Basin

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=1095757971.20130419092931@gmail.com \
    --to=basinilya@gmail.com \
    --cc=esr@thyrsus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.