From: Michael Brand <michael.ch.brand@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bastien <bzg@gnu.org>, Org Mode <emacs-orgmode@gnu.org>,
Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Help on spreadsheet/calc references and improvements
Date: Wed, 30 Oct 2013 18:59:28 +0100 [thread overview]
Message-ID: <CALn3zohHr-sr1w33v4d3EzRK9peUizp9WgSu8do7CDAbotJ7HQ@mail.gmail.com> (raw)
In-Reply-To: <04CCC774-DD9A-4C11-860C-5FA0F378BE34@gmail.com>
Hi Carsten
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:
>>> Applied, thanks.
>>
>> I can not see the commit, is it pushed?
>>
>>> 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.
Hi Carsten
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?
My question about the whereabouts of my patch
0001-Improve-manual-for-table-formulas.patch.txt that is already
"applied" has been overlooked and if I understand correct it is in
your repo but not yet in the main repo. Since the main repo changed
meanwhile, I assume it will create push conflicts on your side. If
this is correct then please get rid of the patch in your repo and I
will take care of the rest.
Michael
next prev parent reply other threads:[~2013-10-30 17:59 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 [this message]
2013-11-13 17:27 ` Michael Brand
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=CALn3zohHr-sr1w33v4d3EzRK9peUizp9WgSu8do7CDAbotJ7HQ@mail.gmail.com \
--to=michael.ch.brand@gmail.com \
--cc=bzg@gnu.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).