On 01/04/2016 10:59 PM, Serhiy Storchaka wrote:
Is it possible to keep the same hashes in both Mercurial and Git? Or
at least the same short hashes?
tl;dr: it's impossible.
The hash is a SHA1 of the revision's "manifest", which contains all the
metadata about the revision. To preserve the
This is now a moot point, but with generaldelta (active by default in hg 3.7)
the hg clone size is at around 400 MB.
Georg
On 01/04/2016 11:53 PM, Alex Gaynor wrote:
> My git clone is 350MB (after a make clean), a fresh hg clone is 650MB.
>
> Alex
>
> On Mon, Jan 4, 2016 at 5:38 PM, Georg Brand
понеділок, 04-січ-2016 15:33:51 R. David Murray написано:
> (Oh, and let me mention this while I'm thinking about it: we're going
> to have to do some extra work to make the hash links work in the bug
> tracker, since I don't think there's any a priori way to distinguish
> between hg hashes and git
понеділок, 04-січ-2016 09:49:57 Eli Bendersky написано:
> I suppose you'll want to use https://github.com/python/cpython, which I'm
> currently maintaining as a read-only mirror. Let me know when you want to
> take control of that repo - I think since it belongs to the "python" Github
> org already
On Tue, Jan 5, 2016 at 7:38 AM, Nick Coghlan wrote:
> On 5 January 2016 at 11:33, R. David Murray wrote:
>> On Tue, 05 Jan 2016 01:26:58 +, "Gregory P. Smith"
>> wrote:
>>> On Mon, Jan 4, 2016 at 12:34 PM R. David Murray
>>> wrote:
>>>
>>> > to have to do some extra work to make the hash l
On 5 January 2016 at 11:33, R. David Murray wrote:
> On Tue, 05 Jan 2016 01:26:58 +, "Gregory P. Smith"
> wrote:
>> On Mon, Jan 4, 2016 at 12:34 PM R. David Murray
>> wrote:
>>
>> > to have to do some extra work to make the hash links work in the bug
>> > tracker, since I don't think there'
The linkifier converts old svn revision numbers to links to e.g.
https://hg.python.org/lookup/r12345 , and this figures out the
equivalent hg changeset and redirects to the corresponding hg.p.o
page.
The linkifier should just create links to
https://hg.python.org/lookup/csid and let the page figure
Probably the easiest thing is to point the linkifier at our own webservice
that just does:
if hash not in cache:
try:
requests.head("github.com/hash")
except requests.error:
try:
request.head("hg.python.org/hash")
except request.error:
re
On Tue, 05 Jan 2016 01:26:58 +, "Gregory P. Smith" wrote:
> On Mon, Jan 4, 2016 at 12:34 PM R. David Murray
> wrote:
>
> > to have to do some extra work to make the hash links work in the bug
> > tracker, since I don't think there's any a priori way to distinguish
> > between hg hashes and g
On Mon, Jan 4, 2016 at 12:34 PM R. David Murray
wrote:
> to have to do some extra work to make the hash links work in the bug
> tracker, since I don't think there's any a priori way to distinguish
> between hg hashes and git hashes.
>
Just ignore the remote possibility of short 32-bit hash prefi
On Mon, Jan 04, 2016 at 07:09:30PM -0500, Donald Stufft wrote:
>
> > On Jan 4, 2016, at 7:06 PM, Trent Nelson
> > wrote:
> >
> > They’re very rough notes but may prove useful. Should *hopefully*
> > be repeatable. One issue I noticed after the fact is that a couple
> > of the renames that happ
> On Jan 4, 2016, at 7:06 PM, Trent Nelson wrote:
>
> Hey Brett, all,
>
> I’m playing a bit of catch-up with e-mail, but it occurred to me some of the
> work I did getting PyParallel switched over to github could be of benefit.
> First thing that comes to mind is this wiki page where I tried to
Hey Brett, all,
I’m playing a bit of catch-up with e-mail, but it occurred to me some of the
work I did getting PyParallel switched over to github could be of benefit.
First thing that comes to mind is this wiki page where I tried to capture the
steps I used for the conversion and subsequent keepi
My git clone is 350MB (after a make clean), a fresh hg clone is 650MB.
Alex
On Mon, Jan 4, 2016 at 5:38 PM, Georg Brandl wrote:
> On 01/01/2016 08:24 PM, Brett Cannon wrote:
> > If you want to read the reasons I chose GitHub over GitLab,
> > see
> https://mail.python.org/pipermail/core-workflow
On 01/01/2016 08:24 PM, Brett Cannon wrote:
> If you want to read the reasons I chose GitHub over GitLab,
> see https://mail.python.org/pipermail/core-workflow/2016-January/000345.html .
> If you want to discuss the decision or help with the transition, please
> subscribe to the core-workflow maili
+1
Alex
On Mon, Jan 4, 2016 at 4:07 PM, Donald Stufft wrote:
>
> > On Jan 4, 2016, at 3:51 PM, Barry Warsaw wrote:
> >
> > I once looked at it and decided it wasn't something I wanted to touch ;)
> so
> > paying Eric to do it might not be a bad idea.
>
>
> I’d prefer it if we didn’t financiall
> On Jan 4, 2016, at 3:51 PM, Barry Warsaw wrote:
>
> I once looked at it and decided it wasn't something I wanted to touch ;) so
> paying Eric to do it might not be a bad idea.
I’d prefer it if we didn’t financially support ESR since he likes to spout off
racist and misogynistic garbage. I’m
On Jan 04, 2016, at 03:33 PM, R. David Murray wrote:
>Maybe The PSF could fund Eric Raymond to do this?
reposurgeon is the tool he developed to port Emacs's bzr repository to git,
and it successfully handled all the previous vcses Emacs was ever developed
under (after, IIRC, much tweaking).
http
On Mon, 04 Jan 2016 18:18:02 +, Brett Cannon wrote:
> On Mon, 4 Jan 2016 at 09:50 Eli Bendersky wrote:
> >
> > I have to admit that I'm not a big expert on Mercurial --> Git converters
> > and the way I maintain this mirror may not be the best approach, so I
> > encourage you folks to find a
On Mon, 4 Jan 2016 at 09:50 Eli Bendersky wrote:
> On Fri, Jan 1, 2016 at 11:24 AM, Brett Cannon wrote:
>
>> If you want to read the reasons I chose GitHub over GitLab, see
>> https://mail.python.org/pipermail/core-workflow/2016-January/000345.html .
>> If you want to discuss the decision or hel
On Fri, Jan 1, 2016 at 11:24 AM, Brett Cannon wrote:
> If you want to read the reasons I chose GitHub over GitLab, see
> https://mail.python.org/pipermail/core-workflow/2016-January/000345.html .
> If you want to discuss the decision or help with the transition, please
> subscribe to the core-wor
On 2 January 2016 at 05:24, Brett Cannon wrote:
> If you want to read the reasons I chose GitHub over GitLab, see
> https://mail.python.org/pipermail/core-workflow/2016-January/000345.html .
> If you want to discuss the decision or help with the transition, please
> subscribe to the core-workflow
Happy 2016 Brett! Thanks for all the care you've put into this decision. I
should also mention that I am happy that as a community we're always
willing to learn -- we've switched VCSes many times before and I expect we
will again in the future. Each time things get better, and I'm looking
forward t
On 01/01/2016 11:24 AM, Brett Cannon wrote:
Happy 2016 everyone, and here is to hoping we will have an easier
developer workflow by the end of this year!
Thanks for doing this, Brett!
I'm looking forward to an easier work flow.
--
~Ethan~
___
pyth
Brett, thank you very much for putting your (vacation!) time into this.
On Fri, Jan 1, 2016, at 11:24, Brett Cannon wrote:
> If you want to read the reasons I chose GitHub over GitLab, see
> https://mail.python.org/pipermail/core-workflow/2016-January/000345.html
> .
> If you want to discuss the d
Brett (and everyone else),
Thanks so much for all the time you put into working through this decision!
Alex
On Fri, Jan 1, 2016 at 2:24 PM, Brett Cannon wrote:
> If you want to read the reasons I chose GitHub over GitLab, see
> https://mail.python.org/pipermail/core-workflow/2016-January/00034
If you want to read the reasons I chose GitHub over GitLab, see
https://mail.python.org/pipermail/core-workflow/2016-January/000345.html .
If you want to discuss the decision or help with the transition, please
subscribe to the core-workflow mailing list.
Happy 2016 everyone, and here is to hoping
27 matches
Mail list logo
