On 08/22/2017 04:33 PM, Andrzej Oleś wrote:
Hi Martin, Nitesh,
thanks for recreating the EBImage repo! I've noticed that even though
the operation helped to fix one commit where the user was previously
unknown:
commit b67438e41b9b7dc62db8c403ee8afd673bd5c0a0
Author: unknown mailto:
Hi Martin, Nitesh,
thanks for recreating the EBImage repo! I've noticed that even though the
operation helped to fix one commit where the user was previously unknown:
commit b67438e41b9b7dc62db8c403ee8afd673bd5c0a0
Author: unknown
Date: Fri Apr 21 13:47:14 2006 +
JWM:Added
Never mind. It's all Patrick Aboyoun, for whom I think this should persist.
Jim
On Tue, Aug 22, 2017 at 4:13 PM, James W. MacDonald wrote:
> Hi Martin and Nitesh,
>
>
> On Tue, Aug 22, 2017 at 10:09 AM, Martin Morgan <
> martin.mor...@roswellpark.org> wrote:
>
>> Thanks for your patience. We up
Hi Martin and Nitesh,
On Tue, Aug 22, 2017 at 10:09 AM, Martin Morgan <
martin.mor...@roswellpark.org> wrote:
> Thanks for your patience. We updated the repositories below; if you cloned
> one of these repositories, you will need to DELETE your clone, and create a
> new clone. If you have added
On 08/22/2017 09:24 AM, Andrzej Oleś wrote:
Hi Martin,
I've just noticed that EBImage, which is on the list of packages not to
be regenerated, is actually affected too (according to the output
below). Therefore, I would like to ask to have it regenerated for the
sake of clean commit history.
Thanks for your patience. We updated the repositories below; if you
cloned one of these repositories, you will need to DELETE your clone,
and create a new clone. If you have added a remote and pulled from these
repositories, you will need to redo the sync. See
https://bioconductor.org/developer
Hi Martin,
I've just noticed that EBImage, which is on the list of packages not to be
regenerated, is actually affected too (according to the output below).
Therefore, I would like to ask to have it regenerated for the sake of clean
commit history.
Thanks,
Andrzej
[oles@localhost EBImage]$ git l
On 08/21/2017 05:30 PM, Stephanie M. Gogarten wrote:
I was actually thinking of SeqVarTools, since I have local commits that
I'm not ready to push yet. GENESIS and GWASdata could be put on the "do
not regenerate" list also - they have no unknown users, and I'd rather
not go through all the step
I was actually thinking of SeqVarTools, since I have local commits that
I'm not ready to push yet. GENESIS and GWASdata could be put on the "do
not regenerate" list also - they have no unknown users, and I'd rather
not go through all the steps again if I don't have to.
thanks,
Stephanie
On 8/
Hi Martin,
Can you check DEGreport? I have made commits already but is not in your list.
I am off the office, so cannot check anything until tomorrow.
Thanks
sent not from my computer
> On Aug 21, 2017, at 16:23, Martin Morgan
> wrote:
>
>> On 08/21/2017 03:17 PM, Stephanie M. Gogarten wrot
On 08/21/2017 03:17 PM, Stephanie M. Gogarten wrote:
If we followed the steps here:
https://www.bioconductor.org/developers/how-to/git/maintain-github-bioc/
How much, if any, of this will need to be redone after the repositories
are regenerated? In particular, if I don't have an unknown user, w
If we followed the steps here:
https://www.bioconductor.org/developers/how-to/git/maintain-github-bioc/
How much, if any, of this will need to be redone after the repositories
are regenerated? In particular, if I don't have an unknown user, will
the regenerated commits be equal to the previous
12 matches
Mail list logo
