git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joey Hess <joey@kitenet.net>
To: git <git@vger.kernel.org>
Subject: Re: usage for git-p2p (was: git pack/unpack over bittorrent - works!)
Date: Sat, 4 Sep 2010 15:29:47 -0400	[thread overview]
Message-ID: <20100904192947.GA15621@gnu.kitenet.net> (raw)
In-Reply-To: <AANLkTin0-Zjy7Chvntf2pNj5iCQ-4Y5u=bu8r7DSejeu@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

Luke Kenneth Casson Leighton wrote:
> ikiwiki is one, and moinmoin can also be configured to use git. Wikis
> have already solved the "conflict" problem, in particular i know that
> joey is a smart bunny and has solved conflict resolution in ikiwiki.

More accurately, I have entirely punted conflict resolution onto the
underlying VCS, such as git, and taken advantage of its generally
excellent merging behavior to avoid the most common classes of things
that result in conflicts/locking on other wikis (like two users editing
different parts of the same page concurrently).

Two branches of a wiki with committers to both can still of course
result in conflicts. In this case, it might make sense to avoid conflict
resolution during merging, and make the conflicted page be committed
containing both versions and some sort of "conflict here!" warning
directive. Then the wiki software can provide an web interface for
cleaning up the conflict later. A custom merge driver could do something
like that, although there's the problem that not all files in the wiki
will be wiki pages, or the conflict could involve conflicting renames of
pages. (Another approach would be to use the "ours" merge strategy.)

-- 
see shy jo, lazy bunny

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      parent reply	other threads:[~2010-09-04 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-04 11:54 usage for git-p2p (was: git pack/unpack over bittorrent - works!) Luke Kenneth Casson Leighton
2010-09-04 15:08 ` Artur Skawina
2010-09-04 15:21   ` Luke Kenneth Casson Leighton
2010-09-04 19:29 ` Joey Hess [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=20100904192947.GA15621@gnu.kitenet.net \
    --to=joey@kitenet.net \
    --cc=git@vger.kernel.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).