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: Mon, 22 Jan 2007 12:08:18 +0100 [thread overview]
Message-ID: <45B49B22.6050806@fs.ei.tum.de> (raw)
In-Reply-To: <200701221056.27599.andyparkins@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
Andy Parkins wrote:
> @@ -876,9 +876,9 @@ sub req_update
> print "MT newline\n";
> next;
> }
> - elsif ( !defined($wrev) || $wrev == 0 )
> + elsif ( (!defined($wrev) || $wrev == 0) && (!defined($meta->{revision}) || $meta->{revision} == 0) )
> {
> - $log->info("Tell the client the file will be added");
> + $log->info("Tell the client the file is scheduled for addition");
This is nice but probably does not handle a collision (cvs output: file was added by a third party) well and will probably overwrite the locally added file. however it is a step in the right direction. from skimming the code I couldn't find collision handling anyways.
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-22 11:08 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
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 [this message]
-- 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=45B49B22.6050806@fs.ei.tum.de \
--to=corecode@fs.ei.tum.de \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
/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).