From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Simon Hausmann <simon@lst.de>
Subject: fast-import maint fixes
Date: Thu, 24 May 2007 00:55:42 -0400 [thread overview]
Message-ID: <20070524045542.GI28023@spearce.org> (raw)
The following changes since commit 7ca055f75ad7ffd2251d4b607fbb86d7bcfd77c7:
Stephan Springl (1):
Use git-for-each-ref to check whether the origin branch exists.
are available in the git repository at:
repo.or.cz:/srv/git/git/fastimport.git maint
Shawn O. Pearce (2):
Refactor fast-import branch creation from existing commit
Fix possible coredump with fast-import --import-marks
Simon Hausmann (2):
fast-import: Fix uninitialized variable
fast-import: Fix crash when referencing already existing objects
fast-import.c | 67 ++++++++++++++++++++++++++---------------------
t/t9300-fast-import.sh | 29 ++++++++++++++++++++
2 files changed, 66 insertions(+), 30 deletions(-)
These are built on top of Junio's maint, and should be merged there,
as they fix coredumps when documented features are actually used.
:-(
--
Shawn.
reply other threads:[~2007-05-24 4:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070524045542.GI28023@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=simon@lst.de \
/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).