From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Peter Krefting <peter@softwolves•pp.se>
Cc: Johan Herland <johan@herland•net>,
Git mailing list <git@vger•kernel.org>
Subject: Re: Having Git follow symlinks
Date: Thu, 30 Jan 2014 13:37:17 +0100 [thread overview]
Message-ID: <vpqa9ed1w8y.fsf@anie.imag.fr> (raw)
In-Reply-To: <alpine.DEB.2.00.1401300958320.30100@ds9.cixit.se> (Peter Krefting's message of "Thu, 30 Jan 2014 10:01:20 +0100 (CET)")
Peter Krefting <peter@softwolves•pp.se> writes:
> Yeah, but then I have copies of the files, instead of having the files
> themselves under version control, meaning I need to copy them back to
> push changes back, or to merge them. That is undesirable :-/
One option is to have the symlink in the other direction: make /etc/foo
a symlink to $GIT_WORKTREE/foo and version the later.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2014-01-30 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 13:49 Having Git follow symlinks Peter Krefting
2014-01-28 14:47 ` Johan Herland
2014-01-30 9:01 ` Peter Krefting
2014-01-30 10:09 ` Christian Couder
2014-01-30 12:37 ` Matthieu Moy [this message]
2014-01-31 9:56 ` Peter Krefting
2014-01-31 13:20 ` Matthew Ruffalo
2014-01-31 17:23 ` Junio C Hamano
2014-01-31 17:56 ` Matthieu Moy
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=vpqa9ed1w8y.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=johan@herland$(echo .)net \
--cc=peter@softwolves$(echo .)pp.se \
/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