From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Simon Hausmann <simon@lst.de>, Alex Riesen <raa.lkml@gmail.com>,
Marius Storm-Olsen <marius@trolltech.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Fix git-p4 on Windows to not use the Posix sysconf
Date: Mon, 16 Jul 2007 01:35:11 -0400 [thread overview]
Message-ID: <20070716053511.GC32566@spearce.org> (raw)
In-Reply-To: <7vmyxydwld.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <gitster@pobox.com> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
>
> > Thanks. Marius' patch was whitespace damaged in the context lines,
> > but it was easily repaired. I've got a couple of other small items
> > in my fastimport repository that I'm going to ask Junio to include
> > in 1.5.3 shortly.
>
> Thanks for taking care of this. I have pulled gfi master into
> 'master'. Perhaps we would want to tag -rc2 this weekend, run
> with it for a week or so and see if we need -rc3 before the
> final.
I'm not entirely sure how we're going to handle the git-p4 patches;
I see there's already another set available to use '-x -' to avoid
command line length problems.
I'm more than happy to play patch monkey and ship them through the
fastimport repository, but since I'm not a p4 user that offers little
value to the process, other than perhaps to save you a little time.
Simon suggested he might setup a git fork on repo.or.cz himself, at
which point you could pull the patches for git-p4 directly from him.
Simon?
--
Shawn.
next prev parent reply other threads:[~2007-07-16 5:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 12:56 [PATCH] Fix git-p4 on Windows to not use the Posix sysconf Marius Storm-Olsen
2007-07-13 13:03 ` Alex Riesen
2007-07-13 13:33 ` Simon Hausmann
2007-07-15 2:49 ` Shawn O. Pearce
2007-07-15 6:12 ` Junio C Hamano
2007-07-16 5:35 ` Shawn O. Pearce [this message]
2007-07-16 7:00 ` Junio C Hamano
2007-07-16 18:30 ` Simon Hausmann
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=20070716053511.GC32566@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marius@trolltech.com \
--cc=raa.lkml@gmail.com \
--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).