From: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Julian Phillips <julian@quantumfyre.co.uk>, git@vger.kernel.org
Subject: Re: incremental fast-import
Date: Fri, 27 Jul 2007 09:44:19 +0200 [thread overview]
Message-ID: <46A9A253.8000602@fs.ei.tum.de> (raw)
In-Reply-To: <20070727005103.GC20052@spearce.org>
Shawn O. Pearce wrote:
> fast-import doesn't assume the local branches already exist.
> It actually assumes its importing from scratch every time. The
> frontend tool needs to restart the branch if that is what it wants.
Is there a compelling reason for this behavior? Shouldn't be so complicated to get an overview on which branches already exist?
Right now I have to do this with a side channel to fast-import, asking the git repo directly, and then "recreating" the branch, etc. Works, but could be nicer, I guess.
cheers
simon
--
Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\
Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
prev parent reply other threads:[~2007-07-27 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 21:47 incremental fast-import Julian Phillips
2007-07-27 0:51 ` Shawn O. Pearce
2007-07-27 7:44 ` Simon 'corecode' Schubert [this message]
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=46A9A253.8000602@fs.ei.tum.de \
--to=corecode@fs.ei.tum.de \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
--cc=spearce@spearce.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).