From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 37988@debbugs.gnu.org
Subject: [bug#37988] why?
Date: Fri, 21 Feb 2020 20:12:46 +0100 [thread overview]
Message-ID: <CAJ3okZ1BwrtKZa8EiwBiuwmmeTy3QrAoLrFPzECgjKc3EqpbVA@mail.gmail.com> (raw)
In-Reply-To: <87blprlr9e.fsf@elephly.net>
Hi Ricardo,
On Fri, 21 Feb 2020 at 19:39, Ricardo Wurmus <rekado@elephly.net> wrote:
> > Why did you pushed your commits instead of mines?
> > Especially when they had not fallen in the crack.
> >
> > I sent them the October 30, 2019.
> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37988
> >
> > And you commented them the same day:
> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37988#26
> >
> > I modified one the November 5th, 2019:
> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37988#47
>
> Uh, that’s odd. I remember working with your r-flow* patches. I did
> not have my own versions of these patches. I know this because I had
> not previously encountered flow cytometry. (I don’t specifically
> remember r-rprotobuflib from this series.)
That's why I found weird the twist. :-)
I thought I did something unexpected and/or there was a special
motivation. And so my "why?". :-)
> My guess is that I wasn’t able to apply them cleanly, so I copy & pasted
> the diff, adjusted as needed, and then forgot to override the commit
> author before pushing :-(
> I’m very sorry to have messed up the authorship here. This was
> definitely not intended :(
I am ok about the authorship; my salary does not depend on the number
of commits accepted. ;-)
The most important is that the packages end in Guix; who committed
them is less important.
Thanks,
simon
prev parent reply other threads:[~2020-02-21 19:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 10:23 [bug#37988] [PATCH 0/6] Add flowWorkspace from BioConductor zimoun
2019-10-30 10:25 ` [bug#37988] [PATCH 1/6] gnu: Add r-idpmisc zimoun
2019-10-30 10:25 ` [bug#37988] [PATCH 2/6] gnu: Add r-flowviz zimoun
2019-10-30 10:25 ` [bug#37988] [PATCH 3/6] gnu: Add r-rprotobuflib zimoun
2019-10-30 11:39 ` Ricardo Wurmus
2019-10-30 13:29 ` zimoun
2019-11-05 17:49 ` [bug#37988] [PATCH v2 " zimoun
2019-11-05 18:19 ` [bug#37988] [PATCH v3 " zimoun
2019-11-05 18:29 ` [bug#37988] [PATCH v4 " zimoun
2019-10-30 10:25 ` [bug#37988] [PATCH 4/6] gnu: Add r-cytolib zimoun
2019-10-30 11:41 ` Ricardo Wurmus
2019-10-30 12:42 ` [bug#37988] [PATCH v2 " zimoun
2019-10-30 10:25 ` [bug#37988] [PATCH 5/6] gnu: Add r-ncdfflow zimoun
2019-10-30 11:42 ` Ricardo Wurmus
2019-10-30 10:25 ` [bug#37988] [PATCH 6/6] gnu: Add r-flowworkspace zimoun
2020-02-21 16:39 ` [bug#37988] why? zimoun
2020-02-21 18:38 ` Ricardo Wurmus
2020-02-21 19:12 ` zimoun [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ1BwrtKZa8EiwBiuwmmeTy3QrAoLrFPzECgjKc3EqpbVA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=37988@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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/guix.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).