emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Brand <michael.ch.brand@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Jason Dunsmore <emacs-orgmode@dunsmor.com>,
	Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Help on spreadsheet/calc references and improvements
Date: Wed, 13 Nov 2013 18:27:00 +0100	[thread overview]
Message-ID: <CALn3zohbc4GT5fjqmUmJHZt=Z_=5rz3vRuWnF=OiTsnaEGRAZw@mail.gmail.com> (raw)
In-Reply-To: <CALn3zohHr-sr1w33v4d3EzRK9peUizp9WgSu8do7CDAbotJ7HQ@mail.gmail.com>

Hi Carsten

On Wed, Oct 30, 2013 at 6:59 PM, Michael Brand
<michael.ch.brand@gmail.com> wrote:
> On Fri, Oct 25, 2013 at 3:31 PM, Carsten Dominik
> <carsten.dominik@gmail.com> wrote:
>> On 24.10.2013, at 22:47, Michael Brand <michael.ch.brand@gmail.com> wrote:
>>> On Thu, Oct 24, 2013 at 8:18 AM, Carsten Dominik
>>> <carsten.dominik@gmail.com> wrote:
>>>> Michael, would you like to have write access to the git repo?
>>>
>>> Thank you for the trust. As I would like anyway to have a review of my
>>> patches before commit, I think it would not help when I would do the
>>> commit myself. I hope that it is still ok when I prefer a review,
>>> independent of the simplicity of the patch.
>>
>> Yes, reviews are always good!  But with write access you can still
>> install a patch yourself after a review, or make small doc fixes
>> without review etc.
>
> Ok, I see that it would help when I "git push" those of my simple
> changes that maybe don't need a review by a maintainer at any price to
> the master branch myself. I already have write access to Worg, do you
> still need my public key?

The last paragraph has not been answered yet. Can I ask Jason Dunsmore
directly to give me write access to Org?

Michael

  reply	other threads:[~2013-11-13 17:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05 14:49 Help on spreadsheet/calc references and improvements Karl Voit
2013-10-05 15:16 ` Michael Brand
2013-10-05 16:08   ` Karl Voit
2013-10-05 16:44     ` Michael Brand
2013-10-06 11:30 ` Karl Voit
2013-10-06 17:03   ` Michael Brand
2013-10-06 18:31     ` Karl Voit
2013-10-06 19:38       ` Michael Brand
2013-10-06 20:06         ` Karl Voit
2013-10-06 20:51           ` Michael Brand
2013-10-18 19:07     ` Michael Brand
2013-10-23 15:12       ` Michael Brand
2013-10-24  6:18         ` Carsten Dominik
2013-10-24 20:47           ` Michael Brand
2013-10-25 10:56             ` Nicolas Goaziou
2013-10-25 13:30               ` Carsten Dominik
2013-10-25 17:03                 ` Nicolas Goaziou
2013-10-25 13:31             ` Carsten Dominik
2013-10-30 17:59               ` Michael Brand
2013-11-13 17:27                 ` Michael Brand [this message]
2013-11-13 17:34                   ` Bastien
2013-11-13 19:42                     ` Michael Brand
2013-11-13 23:21                       ` Bastien

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='CALn3zohbc4GT5fjqmUmJHZt=Z_=5rz3vRuWnF=OiTsnaEGRAZw@mail.gmail.com' \
    --to=michael.ch.brand@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@dunsmor.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).