From: Simon 'corecode' Schubert <corecode@fs•ei.tum.de>
To: Andy Parkins <andyparkins@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] New files in git weren't being downloaded during CVS update
Date: Sat, 20 Jan 2007 11:41:29 +0100 [thread overview]
Message-ID: <45B1F1D9.7090903@fs.ei.tum.de> (raw)
In-Reply-To: <200701201025.31251.andyparkins@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
Andy Parkins wrote:
> On Saturday 2007, January 20 01:19, Simon 'corecode' Schubert wrote:
>
>> I think this is the wrong fix. Reading cvs's classify.c, T_ADDED is
>> only generated for *locally* added files, never for added files in
>> the repo. The correct status would be "U" as well.
>
> I'm sure you're right; I don't know enough about CVS to comment. The
> real fix would seem to be to completely remove the special case for
> added files and let it drop through to the normal update code.
yes, that's what I ment.
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 / \
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-01-20 10:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 10:49 [PATCH] New files in git weren't being downloaded during CVS update 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-21 14:25 Andy Parkins
2007-01-22 2:35 ` Junio C Hamano
2007-01-22 7:02 ` Martin Langhoff
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
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=45B1F1D9.7090903@fs.ei.tum.de \
--to=corecode@fs$(echo .)ei.tum.de \
--cc=andyparkins@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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