emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Konstantin Antipin <antipin.konstantin@googlemail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode mailing list <emacs-orgmode@gnu.org>,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: timer for a task
Date: Thu, 28 May 2009 02:02:51 +0200	[thread overview]
Message-ID: <61176df0905271702t25c02352yd89d05217e3f46c@mail.gmail.com> (raw)
In-Reply-To: <871vqaisdb.fsf@gollum.intra.norang.ca>

Hi all,


On Wed, May 27, 2009 at 3:32 PM, Bernt Hansen <bernt@norang.ca> wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> On May 27, 2009, at 12:13 AM, Konstantin Antipin wrote:
>>
>>> Just a suggestion: why don't we use github for org-mode hosting? It
>>> would be soooo simple to contribute
>>> and to manage things! You would only benefit from this, Carsten.;)
>>> Github is a really nice service. And free, of course.
>>
>> What would be the advantages of using github instead of repo.or.cz?
>> I have found repo.or.cz less polished looking than githib, but very
>> fast and reliable, while github is getting boged down when America
>> wakes up :-)
>
> I don't think there is any advantage to moving to github since you
> already have a hosted working git repo.  If Konstantin wants to share
> his patches all he has to do is make them available somewhere on the net
> so you can pull from his git repo.  He can use github or whatever server
> is convenient for him without requiring you to change your workflow
> (unless you want to of course :) )

You are right indeed, Bernt. I didn't think that my suggestion sounds
like requiring something.
All I wanted to say is that there is such a thing as github and I
think that the effort of migration to it will pay off, especially in
the long run.

And setup github repo instead of sending patches around is a great
idea! (why i didn't think of it earlier?).
That is all I need to put it on github:
   * create repository. two clicks.
   * In org-mode folder:
   git remote add github git@github.com:krick/org-mode.git
   git push github master
Now I can work with both repo.og.cz and github and share my patches
easier. http://github.com/krick/org-mode/tree/master

best,
Konstantin


>
> -Bernt
>

      reply	other threads:[~2009-05-28  0:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25  8:40 timer for a task Konstantin Antipin
2009-05-25  9:25 ` Daniel Clemente
2009-05-25 10:30   ` Konstantin Antipin
2009-05-25 10:44     ` Eraldo Helal
2009-05-25 15:43       ` Konstantin Antipin
2009-05-26 13:18         ` Carsten Dominik
2009-05-26 14:26           ` Konstantin Antipin
2009-05-26 14:45             ` Carsten Dominik
2009-05-26 22:13               ` Konstantin Antipin
2009-05-27  4:27                 ` Carsten Dominik
2009-05-27 13:32                   ` Bernt Hansen
2009-05-28  0:02                     ` Konstantin Antipin [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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=61176df0905271702t25c02352yd89d05217e3f46c@mail.gmail.com \
    --to=antipin.konstantin@googlemail.com \
    --cc=bernt@norang.ca \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).