git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Martin Langhoff <martin@catalyst.net.nz>
Cc: git@vger.kernel.org, Andy Parkins <andyparkins@gmail.com>,
	Frank Lichtenheld <frank@lichtenheld.de>
Subject: Re: [PATCH] cvsserver: Use Merged response instead of Update-existing for merged files
Date: Fri, 09 Mar 2007 17:37:14 -0800	[thread overview]
Message-ID: <7v4pot281h.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <11731741443228-git-send-email-frank@lichtenheld.de> (Frank Lichtenheld's message of "Tue, 6 Mar 2007 10:42:24 +0100")

Frank Lichtenheld <frank@lichtenheld.de> writes:

> Using Update-existing leads to the client forgetting about the "locally
> modified" status of the file which can lead to loss of local changes on
> later updates.

To me, both of these hunks look correct (the first one is clean
merge, the second one is merge with conflicts).  Ack?

> Signed-off-by: Frank Lichtenheld <frank@lichtenheld.de>
> ---
>  git-cvsserver.perl |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/git-cvsserver.perl b/git-cvsserver.perl
> index 1bf892e..65fcc84 100755
> --- a/git-cvsserver.perl
> +++ b/git-cvsserver.perl
> @@ -957,12 +957,12 @@ sub req_update
>              {
>                  $log->info("Merged successfully");
>                  print "M M $filename\n";
> -                $log->debug("Update-existing $dirpart");
> +                $log->debug("Merged $dirpart");
>  
>                  # Don't want to actually _DO_ the update if -n specified
>                  unless ( $state->{globaloptions}{-n} )
>                  {
> -                    print "Update-existing $dirpart\n";
> +                    print "Merged $dirpart\n";
>                      $log->debug($state->{CVSROOT} . "/$state->{module}/$filename");
>                      print $state->{CVSROOT} . "/$state->{module}/$filename\n";
>                      my $kopts = kopts_from_path($filepart);
> @@ -978,7 +978,7 @@ sub req_update
>                  # Don't want to actually _DO_ the update if -n specified
>                  unless ( $state->{globaloptions}{-n} )
>                  {
> -                    print "Update-existing $dirpart\n";
> +                    print "Merged $dirpart\n";
>                      print $state->{CVSROOT} . "/$state->{module}/$filename\n";
>                      my $kopts = kopts_from_path($filepart);
>                      print "/$filepart/1.$meta->{revision}/+/$kopts/\n";
> -- 
> 1.5.0.2

  reply	other threads:[~2007-03-10  1:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06  9:42 [PATCH] cvsserver: Use Merged response instead of Update-existing for merged files Frank Lichtenheld
2007-03-10  1:37 ` Junio C Hamano [this message]
2007-03-11 22:21   ` Martin Langhoff

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=7v4pot281h.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=andyparkins@gmail.com \
    --cc=frank@lichtenheld.de \
    --cc=git@vger.kernel.org \
    --cc=martin@catalyst.net.nz \
    /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).