Am Montag, den 10.10.2011, 22:58 +0200 schrieb Enrico Tröger:
>
> However, Dominic's scripts probably can run on another server as well,
> maybe even on SF's shell servers. Or the whole construct of generating
> those pages can be reworked to be more obvious, easier to test and
> so easier to impr
On Mon, 10 Oct 2011 22:41:19 +0200, Dominic wrote:
>Am Montag, den 10.10.2011, 13:55 +0400 schrieb Alexander Petukhov:
>> By the way, can I gain more control on READMEs on a web-site to be
>> able to modify and then upload and see the result instantly.
>> I was told Dominic maintains this task now
Am Montag, den 10.10.2011, 13:55 +0400 schrieb Alexander Petukhov:
> By the way, can I gain more control on READMEs on a web-site to be
> able to modify and then upload and see the result instantly.
> I was told Dominic maintains this task now.
It's not my servers, so I'm not able to decide this.
On 10/6/11 4:18 PM, Frank Lanitz wrote:
Am 06.10.2011 13:49, schrieb Alexander Petukhov:
well, I uploaded a draft of a README to svn,
I'd suggest to rename it with something like .sample or .template.
Cheers,
Frank
___
Geany-devel mailing list
Geany-
Am 06.10.2011 13:49, schrieb Alexander Petukhov:
> well, I uploaded a draft of a README to svn,
I'd suggest to rename it with something like .sample or .template.
Cheers,
Frank
___
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi
well, I uploaded a draft of a README to svn,
in two words it's structure is like this:
- title
- image (if applicable)
- contents list
- about
- usage
- requrements
- contact info
About is a short paragraph about what a plugin is.
Usage is the place where main information about plugin usage, tip
Am 05.10.2011 22:36, schrieb Matthew Brush:
> I have no problem if you change the Devhelp one, though if we happen to
> move to github, we might want to consider converting them to markdown.
Just a short answer: No. ;)
(Long answer: we discussed this maybe a 100 times before. There is no
real adva
Am 05.10.2011 22:54 schrieb "Alexander Petukhov" :
> does github requires a special README format?
No. Plain text is fine as well as is Markdown or rst.
Take care
Alex
___
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/ma
does github requires a special README format?
___
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On 11-10-05 01:41 PM, Enrico Tröger wrote:
On Wed, 05 Oct 2011 13:36:56 -0700, Matthew wrote:
On 11-10-05 01:23 PM, Alexander Petukhov wrote:
Hi,
when modifying, actually stealing from treebrowser :) a README file,
I came to what if we make plugins webpages of identical format?
They look a li
On Wed, 05 Oct 2011 13:36:56 -0700, Matthew wrote:
>On 11-10-05 01:23 PM, Alexander Petukhov wrote:
>> Hi,
>>
>> when modifying, actually stealing from treebrowser :) a README file,
>> I came to what if we make plugins webpages of identical format?
>> They look a little bit careless now.
>> If nob
On 11-10-05 01:23 PM, Alexander Petukhov wrote:
Hi,
when modifying, actually stealing from treebrowser :) a README file,
I came to what if we make plugins webpages of identical format?
They look a little bit careless now.
If nobody minds I can do this for all plugins,
treebrowser's one looks pre
On Thu, 06 Oct 2011 00:23:54 +0400, Alexander wrote:
>Hi,
>
>when modifying, actually stealing from treebrowser :) a README file,
>I came to what if we make plugins webpages of identical format?
>They look a little bit careless now.
>If nobody minds I can do this for all plugins,
>treebrowser's on
Hi,
when modifying, actually stealing from treebrowser :) a README file,
I came to what if we make plugins webpages of identical format?
They look a little bit careless now.
If nobody minds I can do this for all plugins,
treebrowser's one looks pretty suitable for me as a draft.
E-gards,
Alexand
14 matches
Mail list logo
