Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

[Bill Deegan]

Dirk,

Here's an example on buildbot:
https://github.com/buildbot/buildbot/issues/3564

I see the issue number in the URL..
Or am I missing something when you say you can't see the ID?
-Bill

On Tue, Aug 29, 2017 at 1:46 PM, Dirk Bächle  wrote:

> Bill,
>
>
> On 29.08.2017 22:14, Bill Deegan wrote:
>
>> Dirk,
>>
>> Does the script migrate attachments?
>>
>>
> yes, it also downloads all attachments. But, as mentioned in my other
> post, you can't upload them directly to Github. :(
> And we might create the issues one-by-one in their natural order as you
> suggested, such that the Tigris IDs are kept. But in the normal view under
> Github you can't even see this ID. :(
>
> Regards,
>
> Dirk
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

[Dirk Bächle]

Bill,


On 29.08.2017 22:14, Bill Deegan wrote:

Dirk,

Does the script migrate attachments?



yes, it also downloads all attachments. But, as mentioned in my other 
post, you can't upload them directly to Github. :(
And we might create the issues one-by-one in their natural order as you 
suggested, such that the Tigris IDs are kept. But in the normal view 
under Github you can't even see this ID. :(


Regards,

Dirk

___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

[Dirk Bächle]

Hi Tim,


On 29.08.2017 17:02, Tim Jenness wrote:
If you can add labels during the import then you could conceivably add 
age-based labels such as “ancient”, “1year”, “2years” or whatever. 
Then you would be able to get some feel for which ones are the old 
ones that have been lingering. That combined with ordering by issue 
number should be enough.




this would probably help. But there are some more things to regard 
("problems"?) when migrating to Github. One additional drawback is that 
you can't directly attach files to an issue. I found some links today 
that may give more food for thought:




https://github.com/JamesMGreene/gc2gh-issue-migrator

https://groups.google.com/forum/#!topic/silverstripe-dev/MXBJoYUHTkg

https://stackoverflow.com/questions/7281304/migrate-bugzilla-issues-to-github-issue-tracker 



http://numpy-discussion.10968.n7.nabble.com/Migrating-issues-to-GitHub-td31124.html 




Overall I still see that we'd lose a lot of information and 
functionality, but if we come to the conclusion that we don't actually 
need those...it'll be fine with me. ;)
I just don't want people to scream "bloody murder" afterwards and having 
to do another migration to fix things. ;)


Best regards,

Dirk


___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

[Bill Deegan]

Dirk,

Does the script migrate attachments?

-Bill

On Tue, Aug 29, 2017 at 1:11 PM, Bill Deegan 
wrote:

> People may not know what Tigris is in the near future (or even now)... ;)
>
>
> On Tue, Aug 29, 2017 at 1:00 PM, Tim Jenness  wrote:
>
>> Good idea. Or “Tigris” even.
>>
>> On Aug 29, 2017, at 12:34 , Bill Deegan 
>> wrote:
>>
>> and also "Migrated" tag?
>>
>> On Tue, Aug 29, 2017 at 8:02 AM, Tim Jenness  wrote:
>>
>>> If you can add labels during the import then you could conceivably add
>>> age-based labels such as “ancient”, “1year”, “2years” or whatever. Then you
>>> would be able to get some feel for which ones are the old ones that have
>>> been lingering. That combined with ordering by issue number should be
>>> enough.
>>>
>>> On Aug 29, 2017, at 07:41, Bill Deegan 
>>> wrote:
>>>
>>> Looks like you can't specify the issue #, but it's a safe bet their
>>> sequential, so if we create each and every bug which is on tigris...
>>>
>>> https://developer.github.com/v3/issues/#create-an-issue
>>>
>>> On Tue, Aug 29, 2017 at 12:00 AM, Dirk Baechle  wrote:
>>>
 Bill,

 I haven't checked this. But I'd expect to have this 1:1 mapping for
 Tigris->NewTracker anyway. If Github wouldn't support this it'd be a nogo
 for me.

 I'll try to have another look at the API today. If someone here knows
 more, chime in please.

 Regards,

 Dirk
 --
 Sent from my Android with K-9 Mail.
>>>
>>>
>>> ___
>>> Scons-dev mailing list
>>> Scons-dev@scons.org
>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>
>>>
>>>
>>> ___
>>> Scons-dev mailing list
>>> Scons-dev@scons.org
>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>>
>>>
>> ___
>> Scons-dev mailing list
>> Scons-dev@scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>>
>>
>> ___
>> Scons-dev mailing list
>> Scons-dev@scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

[Bill Deegan]

People may not know what Tigris is in the near future (or even now)... ;)


On Tue, Aug 29, 2017 at 1:00 PM, Tim Jenness  wrote:

> Good idea. Or “Tigris” even.
>
> On Aug 29, 2017, at 12:34 , Bill Deegan  wrote:
>
> and also "Migrated" tag?
>
> On Tue, Aug 29, 2017 at 8:02 AM, Tim Jenness  wrote:
>
>> If you can add labels during the import then you could conceivably add
>> age-based labels such as “ancient”, “1year”, “2years” or whatever. Then you
>> would be able to get some feel for which ones are the old ones that have
>> been lingering. That combined with ordering by issue number should be
>> enough.
>>
>> On Aug 29, 2017, at 07:41, Bill Deegan  wrote:
>>
>> Looks like you can't specify the issue #, but it's a safe bet their
>> sequential, so if we create each and every bug which is on tigris...
>>
>> https://developer.github.com/v3/issues/#create-an-issue
>>
>> On Tue, Aug 29, 2017 at 12:00 AM, Dirk Baechle  wrote:
>>
>>> Bill,
>>>
>>> I haven't checked this. But I'd expect to have this 1:1 mapping for
>>> Tigris->NewTracker anyway. If Github wouldn't support this it'd be a nogo
>>> for me.
>>>
>>> I'll try to have another look at the API today. If someone here knows
>>> more, chime in please.
>>>
>>> Regards,
>>>
>>> Dirk
>>> --
>>> Sent from my Android with K-9 Mail.
>>
>>
>> ___
>> Scons-dev mailing list
>> Scons-dev@scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>>
>>
>> ___
>> Scons-dev mailing list
>> Scons-dev@scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
>>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

[Bill Deegan]

and also "Migrated" tag?

On Tue, Aug 29, 2017 at 8:02 AM, Tim Jenness  wrote:

> If you can add labels during the import then you could conceivably add
> age-based labels such as “ancient”, “1year”, “2years” or whatever. Then you
> would be able to get some feel for which ones are the old ones that have
> been lingering. That combined with ordering by issue number should be
> enough.
>
> On Aug 29, 2017, at 07:41, Bill Deegan  wrote:
>
> Looks like you can't specify the issue #, but it's a safe bet their
> sequential, so if we create each and every bug which is on tigris...
>
> https://developer.github.com/v3/issues/#create-an-issue
>
> On Tue, Aug 29, 2017 at 12:00 AM, Dirk Baechle  wrote:
>
>> Bill,
>>
>> I haven't checked this. But I'd expect to have this 1:1 mapping for
>> Tigris->NewTracker anyway. If Github wouldn't support this it'd be a nogo
>> for me.
>>
>> I'll try to have another look at the API today. If someone here knows
>> more, chime in please.
>>
>> Regards,
>>
>> Dirk
>> --
>> Sent from my Android with K-9 Mail.
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

[Tim Jenness]

If you can add labels during the import then you could conceivably add 
age-based labels such as “ancient”, “1year”, “2years” or whatever. Then you 
would be able to get some feel for which ones are the old ones that have been 
lingering. That combined with ordering by issue number should be enough.

> On Aug 29, 2017, at 07:41, Bill Deegan  wrote:
> 
> Looks like you can't specify the issue #, but it's a safe bet their 
> sequential, so if we create each and every bug which is on tigris...
> 
> https://developer.github.com/v3/issues/#create-an-issue 
> 
> 
> On Tue, Aug 29, 2017 at 12:00 AM, Dirk Baechle  > wrote:
> Bill,
> 
> I haven't checked this. But I'd expect to have this 1:1 mapping for 
> Tigris->NewTracker anyway. If Github wouldn't support this it'd be a nogo for 
> me. 
> 
> I'll try to have another look at the API today. If someone here knows more, 
> chime in please. 
> 
> Regards, 
> 
> Dirk
> -- 
> Sent from my Android with K-9 Mail.
> 
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev

___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

[Bill Deegan]

Looks like you can't specify the issue #, but it's a safe bet their
sequential, so if we create each and every bug which is on tigris...

https://developer.github.com/v3/issues/#create-an-issue

On Tue, Aug 29, 2017 at 12:00 AM, Dirk Baechle  wrote:

> Bill,
>
> I haven't checked this. But I'd expect to have this 1:1 mapping for
> Tigris->NewTracker anyway. If Github wouldn't support this it'd be a nogo
> for me.
>
> I'll try to have another look at the API today. If someone here knows
> more, chime in please.
>
> Regards,
>
> Dirk
> --
> Sent from my Android with K-9 Mail.
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Problematic conflicts between C/C++ and D

[Bill Deegan]

env.get is just like a python dictionary.

the order will depend on the order the tools are loaded into the
Environment()..

On Tue, Aug 29, 2017 at 5:48 AM, Russel Winder  wrote:

> On Mon, 2017-08-28 at 15:41 -0700, Bill Deegan wrote:
> > so a better solution would be:
> >
> > env['SHOBJSUFFIX'] = env.get('SHOBJSUFFIX','.os')
> >
> > ?
>
> I am not sure. What is the semantics of the env.get function, and who
> gets to set the SHOBJSUFFIX and when?
>
> --
> Russel.
> 
> =
> Dr Russel Winder  t: +44 20 7585 2200   voip:
> sip:russel.win...@ekiga.net
> 41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Problematic conflicts between C/C++ and D

[Russel Winder]

On Mon, 2017-08-28 at 15:41 -0700, Bill Deegan wrote:
> so a better solution would be:
> 
> env['SHOBJSUFFIX'] = env.get('SHOBJSUFFIX','.os')
> 
> ?

I am not sure. What is the semantics of the env.get function, and who
gets to set the SHOBJSUFFIX and when? 
 
-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

signature.asc
Description: This is a digitally signed message part
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] SCons, Mercurial, BitBucket, Git, and GitHub

[Dirk Baechle]

Bill,

I haven't checked this. But I'd expect to have this 1:1 mapping for 
Tigris->NewTracker anyway. If Github wouldn't support this it'd be a nogo for 
me. 

I'll try to have another look at the API today. If someone here knows more, 
chime in please. 

Regards, 

Dirk
-- 
Sent from my Android with K-9 Mail.___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev