emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: commit 7b9f2fba66
Date: Tue, 26 Jan 2016 18:11:59 +0100	[thread overview]
Message-ID: <87d1sow9i8.fsf@Rainer.invalid> (raw)
In-Reply-To: 20160126001121.GA2551@laboissiere.net

Rafael Laboissiere writes:
> I am the author of the commits and I sincerely apologize for breaking
> the usual rules of development of Org-mode.

Thanks.

> I contributed in the past to both Worg and Org-mode itself.  I do not
> remember who gave me push access to the Git repositories, it was some
> years ago.  I have forgotten that all my contributions and patches to
> Org-mode where integrated by others into Git.  This time, when I fixed
> the bugs in my commits 860bcfb and 7b9f2fb, I thought that I have
> pushed changes in the past myself.  Sorry for the confusion.

It's quite likely you were supposed to have access to Worg.  That
shouldn't give you commit access to the Org repository however.  So I'd
still would like to know how you've gotten the latter part, since this
seems to indicate some oversight somewhere.  Somebody with access to the
server config should at least check that all people with permission to
commit have assigned copyright to the FSF, IMHO.

> As a matter of fact, none of those two commits introduced changes in
> functionality.

Thanks.  If you commit something to maint, you're supposed to merge that
bugfix back into master yourself.

> Nicolas Goaziou contacted me privately and suggested to get the
> copyright assignment from FSF.  I am about to sent the form to them
> and will keep you informed when it is finished.  In the meanwhile, I
> will send my patches to the ML, if there will be any.

Getting the copyright assigned would be good since if you've had some
previous changes (not the two commits you did yourself), then quite
likely you've already exhausted your TINYCHANGE budget.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2016-01-26 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 10:24 commit 860bcfbf93 Achim Gratz
2016-01-25 18:34 ` commit 7b9f2fba66 (was: commit 860bcfbf93) Achim Gratz
2016-01-26  0:11   ` Rafael Laboissiere
2016-01-26 17:11     ` Achim Gratz [this message]
2016-03-12  9:59       ` commit 7b9f2fba66 Rafael Laboissiere
2016-01-26  2:06   ` font bug in 0.9.16 Robert Horn
2016-01-26 14:10     ` Robert Horn

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=87d1sow9i8.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).