unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Roel Janssen <roel@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Updating to latest Bioconductor release
Date: Thu, 19 Nov 2020 20:18:14 +0100	[thread overview]
Message-ID: <CAJ3okZ0Wdv7yntAYX1cX-=3zLbytYv=Ui1nCukrLKBz0s4sbGQ@mail.gmail.com> (raw)
In-Reply-To: <ec6649628a5bf6b731070663e2f8a209a3f11875.camel@gnu.org>

Hi Roel,

On Thu, 19 Nov 2020 at 20:03, Roel Janssen <roel@gnu.org> wrote:

> > http://logs.guix.gnu.org/guix/2020-11-19.log#182349

> Right, so I shouldn't have pushed to "wip-r" in the first place.

Well, I think it is a lack of synchronisation between all of 3;
especially with this work around via external GitHub upstream.


> Perhaps I should do it "the old way" and base my patches on the master
> branch and send the gazillion patches to the mailing list. :)

What Ricardo did previously (my rewrite of history on Nov. 10 on
GitHub, and then pushed by Ricardo to Savannah today), quoting their
word: "delete origin/wip-r, reset my local copy to zimoun/wip-r,
rebased on top of origin/master, and pushed origin/wip-r".  Maybe you
could do the same.

Or if you have the super power to do that: you can delete the branch
and re-push.


> Then we can discuss each line of the commit messages separately before
> pushing to the master branch.

Well, I do not know what Ricardo thinks, but personally I would prefer
first a wip-r branch then merge.  It will avoid avoid annoyance of
possible broken packages, I mean we could detect them.


All the best,
simon


  reply	other threads:[~2020-11-19 19:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 10:49 Updating to latest Bioconductor release Roel Janssen
2020-11-16 11:27 ` zimoun
2020-11-16 12:10   ` Roel Janssen
2020-11-16 12:29     ` zimoun
2020-11-16 12:38       ` Roel Janssen
2020-11-16 12:59         ` zimoun
2020-11-17 22:58 ` zimoun
2020-11-18  9:31   ` Roel Janssen
2020-11-18 11:50     ` zimoun
2020-11-18 16:13       ` Roel Janssen
2020-11-18 16:23         ` zimoun
2020-11-18 16:33           ` Roel Janssen
2020-11-18 16:59             ` zimoun
2020-11-19 15:31               ` Roel Janssen
2020-11-19 15:36                 ` zimoun
2020-11-19 15:57                   ` Roel Janssen
2020-11-19 16:18                     ` zimoun
2020-11-19 16:25                       ` Roel Janssen
2020-11-19 16:36                         ` zimoun
2020-11-19 17:27                         ` zimoun
2020-11-19 19:03                           ` Roel Janssen
2020-11-19 19:18                             ` zimoun [this message]
2020-11-19 21:13                               ` Ricardo Wurmus
2020-11-20  9:16                                 ` Roel Janssen
2020-11-20 13:39                                   ` Ricardo Wurmus
2020-11-20 13:42                                     ` Ricardo Wurmus
2020-11-20 14:02                                       ` zimoun
2020-11-20 14:10                                       ` Roel Janssen
2020-11-20 13:59                                     ` zimoun
2020-11-20 14:28                                       ` Ricardo Wurmus
2020-11-20 15:20                                         ` zimoun

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='CAJ3okZ0Wdv7yntAYX1cX-=3zLbytYv=Ui1nCukrLKBz0s4sbGQ@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=roel@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/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).