From: Petr Baudis <pasky@suse.cz>
To: Pavel Roskin <proski@gnu.org>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] cg-pull to stop treating "master" specially, fix fetch_local for .git/HEAD
Date: Thu, 10 Nov 2005 20:24:30 +0100 [thread overview]
Message-ID: <20051110192430.GS30496@pasky.or.cz> (raw)
In-Reply-To: <1124832796.23795.9.camel@dv>
Hello,
Dear diary, on Tue, Aug 23, 2005 at 11:33:16PM CEST, I got a letter
where Pavel Roskin <proski@gnu.org> said that...
> Local URL handling needs to be fixed to handle .git/HEAD properly, since
> it's a symlink in the upstream directory. A new flag "-b" for fetch_*
> functions is introduced, meaning "dereference" (like in GNU cp).
>
> @@ -205,6 +209,11 @@ fetch_local()
> [ "$1" = "-s" ] && shift
>
> cp_flags_l="-vdpR"
> + if [ "$1" = "-b" ]; then
> + cp_flags_l="-vb" # Dereference symlinks
> + shift
> + fi
> +
> if [ "$1" = "-u" ]; then
> cp_flags_l="$cp_flags_l -fu$can_hardlink"
> suggest_hardlink=
can you still remember why did you introduce this? In GNU cp
documentation, I can see just
-b, --backup
Make backups of files that are about to be overwritten or removed.
which doesn't make sense to me - -L dereferences symlinks.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-11-10 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 21:33 [PATCH] cg-pull to stop treating "master" specially, fix fetch_local for .git/HEAD Pavel Roskin
2005-11-10 19:24 ` Petr Baudis [this message]
2005-11-10 20:11 ` Pavel Roskin
2005-11-10 23:26 ` Josef Weidendorfer
2005-11-10 23:40 ` Petr Baudis
2005-11-10 23:56 ` Josef Weidendorfer
2005-11-11 0:09 ` Petr Baudis
2005-11-11 0:14 ` Pavel Roskin
2005-11-11 1:13 ` Josef Weidendorfer
2005-11-11 4:53 ` Pavel Roskin
2005-11-11 14:22 ` Josef Weidendorfer
2005-11-11 15:26 ` Pavel Roskin
2005-11-11 16:10 ` Josef Weidendorfer
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=20051110192430.GS30496@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=proski@gnu.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).