From: "Shawn O. Pearce" <spearce@spearce.org>
To: Simon Hausmann <simon@lst.de>
Cc: git@vger.kernel.org
Subject: Re: merging git-p4 into git/fastimport.git (second try)
Date: Fri, 22 Jun 2007 19:20:02 -0400 [thread overview]
Message-ID: <20070622232002.GJ17393@spearce.org> (raw)
In-Reply-To: <200706190842.13175.simon@lst.de>
Simon Hausmann <simon@lst.de> wrote:
> Why not just leave out the entire lot of git-p4 logs in "What's in git.git"
> this one time? I'm not sure of how much value it is at this point anyway. I'm
> just interested in preserving the history to ease debugging.
Yeah, maybe a good idea. That's now up to Junio. I just pulled
your git-p4 branch into my fastimport, and republished it.
--
Shawn.
prev parent reply other threads:[~2007-06-22 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 22:35 merging git-p4 into git/fastimport.git (second try) Simon Hausmann
2007-06-18 23:00 ` Shawn O. Pearce
2007-06-19 6:42 ` Simon Hausmann
2007-06-22 23:20 ` Shawn O. Pearce [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=20070622232002.GJ17393@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--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).