From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org, "Andy Parkins" <andyparkins@gmail.com>
Subject: Re: [PATCH] New files in git weren't being downloaded during CVS update
Date: Mon, 22 Jan 2007 20:02:29 +1300 [thread overview]
Message-ID: <46a038f90701212302v458019fcxcde72a34aa46e7bd@mail.gmail.com> (raw)
In-Reply-To: <7vmz4bwzy4.fsf@assigned-by-dhcp.cox.net>
On 1/22/07, Junio C Hamano <junkio@cox.net> wrote:
> > This is in response to Simon Schubert's suggestion that T_ADDED is an
> > inappropriate category for a remotely added file. Instead this treats
> > remotely added files the same as remotely changed files.
>
> Martin, I think this looks like a sane change.
It does -- sorry I've been offline for a few days and catching up with work.
> I do not have anything other than the real CVS running on a
> Linux box to try this change (most notably I do not do Eclipse
> nor Tortoise) myself and I am reluctant to touch things I cannot
> personally test at this stage near the release.
Fair enough. I'll give it whirl later tonight. For a quick test, you can always
export CVS_SERVER=/home/martin/src/git/git-cvsserver.perl
cvs update
> tested this for his own use in his environment, but I would
> really appreciate a third party Ack from an environment
> different from the originator of the patch.
Yup. Will test later tonight.
martin
next prev parent reply other threads:[~2007-01-22 7:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 14:25 [PATCH] New files in git weren't being downloaded during CVS update Andy Parkins
2007-01-22 2:35 ` Junio C Hamano
2007-01-22 7:02 ` Martin Langhoff [this message]
2007-01-22 7:16 ` Junio C Hamano
2007-01-22 10:44 ` Andy Parkins
2007-01-22 10:46 ` Andy Parkins
2007-01-22 10:56 ` Andy Parkins
2007-01-22 11:08 ` Simon 'corecode' Schubert
-- strict thread matches above, loose matches on Subject: below --
2007-01-19 10:49 Andy Parkins
2007-01-20 1:19 ` Simon 'corecode' Schubert
2007-01-20 10:25 ` Andy Parkins
2007-01-20 10:41 ` Simon 'corecode' Schubert
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=46a038f90701212302v458019fcxcde72a34aa46e7bd@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).