On 02.07.2019 17:47, Smith, Madison (CGI Federal) wrote:
>
> Good morning SVN Devs!
>
>
>
> I've been looking at the roadmap and was wondering why there isn't any
> push to move to Python 3?
>
>
>
> Python 2 support ends at the end of the year...in 3 months! Many big
> businesses, contractors,
Imagine working on one larger feature (or even multiple features). You
already have created a couple of local commits, but are not yet
finished. Following use cases come to my mind:
1) some other developer commits new revisions
- it should be possible to continue working on your feature-queue
On Fri, Jun 28, 2019 at 12:51 PM Markus Schaber
wrote:
> It's a very powerful feature, on par or even superior to other (D)VCSes -
> as long as we manage to keep the interface clear enough that users can
> handle everything.
>
> I'm always astonished how complicated GIT can be for seemingly "simp
On Sun, Jun 30, 2019 at 11:22 AM Thomas Singer
wrote:
> With "rebasing" I mean, that such list of "local commits" needs to be
> re-applied (on demand, not automatically) onto a different revision.
> Something like a continues series of cherry-picking (with the
> possibility to get a conflict in e
Good morning SVN Devs!
I've been looking at the roadmap and was wondering why there isn't any push to
move to Python 3?
Python 2 support ends at the end of the year...in 3 months! Many big
businesses, contractors, etc that use this product for years will no longer be
able to as they have p
I finally got one step further on my ARM build slave project. This is a
Raspberry Pi 4 B with 2 gigs of RAM:
sysop@pihole:~ $ uname -a
Linux pihole 4.19.50-v7l+ #895 SMP Thu Jun 20 15:03:42 CET 2019 armv7l GNU/Linux
sysop@pihole:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Rasp
6 matches
Mail list logo
