From: Clemens Buchacher <drizzd@aon.at>
To: "J.H." <warthog19@eaglescrag.net>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
Pieter de Bie <pieter@frim.nl>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Petr Baudis <pasky@suse.cz>,
git@vger.kernel.org
Subject: Re: [RFC] Git Wiki Move
Date: Sat, 16 Jan 2010 11:17:05 +0100 [thread overview]
Message-ID: <20100116101705.GA28821@localhost> (raw)
In-Reply-To: <4B5113FD.9020004@eaglescrag.net>
On Fri, Jan 15, 2010 at 05:18:53PM -0800, J.H. wrote:
> On 01/15/2010 04:44 PM, Sverre Rabbelier wrote:
> > On Sat, Jan 16, 2010 at 01:28, J.H. <warthog19@eaglescrag.net> wrote:
> >>> <!-- GitLink[git-name] Because Linus is an egotistical git -->
> >>
> >> Probably, should be fixed now, found it on GitBot too.
> >
> > I guess you removed them rather than turning them in to comments
> > (probably due to MediaWiki's lake of comments)? Works for me, we can
> > figure out something else for gitbot. A regular text file that it can
> > slurp or something. We being Pieter perhaps (as he is the original author)?
> >
>
> The templates giving me a PITA trying to get it to actually generate a
> comment, easiest thing might be to hide it in the span or something, or
> add the comments in manually.
>
While we are at it, it would be good to put gitlink's past the section
name, so that it is available when using section editing (the lack of which
was a huge PITA in moinmoin).
Also, it would be better to actually show the gitlink name and comment with
the regular content. Maybe using a special tag which makes it look like a
comment. For example
== Why won't I see changes in the remote repo after "git push"? ==
{{gitlink|non-bare|Pushing to non-bare repositories is discouraged}}
which gets translated to
<div id="contentSub">
non-bare -- Pushing to non-bare repositories is discouraged
</div>
Clemens
next prev parent reply other threads:[~2010-01-16 10:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 23:29 [ANNOUNCE] Git wiki & repo.or.cz migration, donations and volunteers pledge Petr Baudis
2010-01-14 1:24 ` [RFC] Git Wiki Move Petr Baudis
2010-01-14 10:28 ` J.H.
2010-01-14 10:35 ` Matthieu Moy
2010-01-14 18:56 ` J.H.
2010-01-15 23:18 ` J.H.
2010-01-15 23:21 ` Sverre Rabbelier
2010-01-15 23:50 ` Junio C Hamano
2010-01-16 0:05 ` J.H.
2010-01-16 0:02 ` J.H.
2010-01-16 0:08 ` Sverre Rabbelier
2010-01-16 0:12 ` Junio C Hamano
2010-01-16 0:28 ` J.H.
2010-01-16 0:44 ` Sverre Rabbelier
2010-01-16 1:18 ` J.H.
2010-01-16 10:17 ` Clemens Buchacher [this message]
2010-01-17 12:00 ` Matthieu Moy
2010-01-17 23:06 ` Johannes Schindelin
2010-01-18 0:43 ` J.H.
2010-01-18 9:53 ` Johannes Schindelin
2010-01-18 12:03 ` Johannes Schindelin
2010-01-18 18:47 ` J.H.
2010-01-18 20:46 ` Johannes Schindelin
2010-01-21 21:35 ` Petr Baudis
2010-01-22 0:21 ` Jakub Narebski
2010-01-22 0:31 ` Petr Baudis
2010-01-22 0:39 ` Johannes Schindelin
2010-01-14 10:43 ` Johannes Schindelin
2010-01-14 11:01 ` Johannes Schindelin
2010-01-14 18:52 ` J.H.
2010-01-14 10:48 ` Petr Baudis
2010-01-14 11:03 ` Johannes Schindelin
2010-02-12 11:38 ` Petr Baudis
2010-01-14 10:48 ` Wincent Colaiuta
2010-01-15 17:17 ` Joey Hess
2010-01-15 19:16 ` Johannes Schindelin
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=20100116101705.GA28821@localhost \
--to=drizzd@aon.at \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=pieter@frim.nl \
--cc=srabbelier@gmail.com \
--cc=warthog19@eaglescrag.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.