From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Git List <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Derrick Stolee <dstolee@microsoft.com>
Subject: Re: [PATCH v2 3/3] gitfaq: add entry about syncing working trees
Date: Mon, 08 Nov 2021 14:09:42 -0800 [thread overview]
Message-ID: <xmqqmtmes3ix.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cRtOpaPd_HCQAW=33-vxhP4Knijo3g0dUA9HVb4_=JH4w@mail.gmail.com> (Eric Sunshine's message of "Sun, 7 Nov 2021 19:12:14 -0500")
Eric Sunshine <sunshine@sunshineco.com> writes:
> Taking into consideration that people who are experiencing such
> corruption will likely include the name of the syncing service in
> their search query, would it make sense to mention some well-known
> services here in order to make it more likely that people will
> actually find this entry? Something like this, perhaps:
>
> It is important not to use a cloud syncing service (such as DropBox,
> FooBar, CowMoo, BuzzingBee, etc.) to sync any portion of a Git
> repository...
I do agree that in a repository being actively modified, any
backup/sync solution that works per-file fashion would not work
well. But is "cloud" a good word to characterise and group these
per-file backup/sync solution?
Doesn't rsync work the same per-file fashion, and the only reason
why it is a better fit is because it is not continuous, not
attempting to "sync" while the repository is in use, until the user
explicitly says "OK, I am ready to go home, so let's stop working
here and send everything over to home with rsync"?
>> +* There are no additional worktrees enabled for your repository.
>
> I don't fully understand this restriction. Can you explain it (at
> least here in the email discussion)?
>
>> +* You are not using a separate Git directory outside of your repository root.
>
> Same question about this restriction.
As long as you know what you are doing and catch everything in
quiescent state, you should be fine, I would think.
next prev parent reply other threads:[~2021-11-08 22:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 22:55 [PATCH v2 0/3] Additional FAQ entries brian m. carlson
2021-11-07 22:55 ` [PATCH v2 1/3] gitfaq: add documentation on proxies brian m. carlson
2021-11-07 23:27 ` Eric Sunshine
2021-11-08 1:53 ` brian m. carlson
2021-11-08 21:24 ` Junio C Hamano
2022-01-04 13:40 ` Johannes Schindelin
2021-11-07 22:55 ` [PATCH v2 2/3] gitfaq: give advice on using eol attribute in gitattributes brian m. carlson
2021-11-07 23:48 ` Eric Sunshine
2021-11-08 2:09 ` brian m. carlson
2021-11-07 22:55 ` [PATCH v2 3/3] gitfaq: add entry about syncing working trees brian m. carlson
2021-11-08 0:12 ` Eric Sunshine
2021-11-08 22:09 ` Junio C Hamano [this message]
2021-11-09 0:10 ` Junio C Hamano
2021-11-14 23:40 ` brian m. carlson
[not found] ` <YYmmBMkwy6bpVpzI@camp.crustytoothpaste.net>
2021-11-09 0:02 ` Eric Sunshine
2021-11-08 0:16 ` [PATCH v2 0/3] Additional FAQ entries Eric Sunshine
2022-01-04 13:53 ` Johannes Schindelin
2022-01-04 13:54 ` Johannes Schindelin
2022-01-06 1:58 ` brian m. carlson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqmtmes3ix.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=bagasdotme@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).