From: Angus Hammond <angusgh@gmail.com>
To: Steven Penny <svnpenn@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git stash destroys hard links
Date: Tue, 22 May 2012 18:52:00 +0100 [thread overview]
Message-ID: <CAOBOgRYtMi38f63G2Nzd3--FsmN0F8geFi-AHxL2L2MMHWHFHA@mail.gmail.com> (raw)
In-Reply-To: <CAAXzdLWadNg9d_i8fZTawaxYm3ytcGCT4pzeth=LxrQYEO-3ww@mail.gmail.com>
>From the very quick and unscientific test that I just did, it doesn't
appear that git commits hard links, it just collapses them into
separate regular files (presumably to avoid changes in one place
mucking things up elsewhere without git knowing about it). I don't
think it makes much sense to stash hardlinks if the policy is to
forget them in commits.
Thanks
Angus
prev parent reply other threads:[~2012-05-22 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 4:24 git stash destroys hard links Steven Penny
2012-05-22 17:41 ` Junio C Hamano
2012-05-22 17:52 ` Angus Hammond [this message]
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=CAOBOgRYtMi38f63G2Nzd3--FsmN0F8geFi-AHxL2L2MMHWHFHA@mail.gmail.com \
--to=angusgh@gmail.com \
--cc=git@vger.kernel.org \
--cc=svnpenn@gmail.com \
/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).